Code:
- Importer resolveRecord (simplified):
``` php
<?php
public function resolveRecord(): ?DailyGift
{
    $dailyGift = DailyGift::query()
        ->where('day', $this->data['day'])
        ->first();

    if (! $dailyGift) {
        throw new RowImportFailedException("No Daily Gift found for Day [{$this->data['day']}].");
    }

    return $dailyGift;
}
```
- Auth config (relevant parts):
``` php
<?php
'defaults' => [
    'guard' => env('AUTH_GUARD', 'web'),
],
'guards' => [
    'web' => ['driver' => 'session', 'provider' => 'users'],
    'gamer' => ['driver' => 'sanctum', 'provider' => 'gamers'],
    'admin' => ['driver' => 'session', 'provider' => 'admins'],
],
'providers' => [
    'users' => ['driver' => 'eloquent', 'model' => App\Models\User::class],
    'gamers' => ['driver' => 'eloquent', 'model' => App\Models\Gamer::class],
    'admins' => ['driver' => 'eloquent', 'model' => App\Models\Admin::class],
],
```
- Admin panel uses admin guard:
``` php
<?php
$panel
    ->authGuard('admin')
    ->id('admin')
    ->path('admin')
    ->login();
```
- imports table row (summarized):
    - id: 1
    - file_name: daily-gift-importer-example (2).csv
    - importer: App\Filament\Imports\DailyGiftImporter
    - total_rows: 1
    - successful_rows: 0
    - user_id: 1
    - completed_at: NULL

Question(s):
- How can I ensure Filament’s ImportCsv queued job authenticates using the admin guard for the import’s user, without changing my global default guard or breaking other workers?
- Is there a way for Filament Actions to persist the panel/guard context on the import and use it when the job runs? Do I need to publish/run additional Filament Actions migrations so the job knows the panel/guard (e.g., panel_id/user_type)?
- Alternatively, can I dispatch the ImportCsv job to a dedicated queue and run a worker for that queue that uses the admin guard only for those jobs, while keeping my other workers unchanged? If so, what’s the recommended way to set the queue name for ImportAction/ImportCsv?