[13.x] Allow Jobs to include context

[jackbayliss]

Happy bday week!

When inspecting queued jobs or handling job events, you often just want a bit more context , especially during deployments. This is different from global "world" illuminate:log:context and more about the job context itself the job doesn't have to run for us to have this context just be dispatched.

I made a video to also cover this... (audio on, bit boring)

Screen.Recording.2026-05-26.at.12.53.59.mov

This PR adds a HasContext interface, which adds context into the job payload, implement it on your job and return whatever is useful:

class AgentJob implements ShouldQueue, HasContext
{
    public function context(): array
    {
        return [
            'provider' => $this->provider,
            'model'    => $this->model,
        ];
    }
}

Then when inspecting the queue we can access it:

  Queue::reservedJobs()->first()->context

Or in a listener access the context we need... no need to dig in the payload

  public function handle(JobProcessing $event): void
  {
      Log::error('Processing Job', [
          'job' => $event->job->resolveName(),
          ...$event->job->context() ?? [],
      ]);
  }

The context is completely controlled in userland, and completely opt in.

Used an interface cause I can't think of a nicer non b/c way , perhaps in 14.x we could method_exists if you don't like it, but I thought it was ok for now.

This is my eyes would also be very cool to surface to monitoring services too such as Telescope, etc.

This means we can go logging from reservedJobs from:

[11:50:11] Deployment waiting for App\Jobs\AgentJob

To

[11:50:11] Deployment waiting for App\Jobs\AgentJob {"provider":"anthropic","model":"claude-sonnet-4-20250514"}

Specific to the job, and all contained within that job...

Any adjustments, have at it, or let me know where to tweak ... happy to rename too maybe metadata is more fitting?

[github-actions]

Thanks for submitting a PR!

Note that draft PRs are not reviewed. If you would like a review, please mark your pull request as ready for review in the GitHub user interface.

Pull requests that are abandoned in draft may be closed due to inactivity.