feat: job worker

[0xgleb]

Motivation

ADR-0001 lifts a supervised job-execution stack into event-sorcery. With the
Job trait in place (#11), the next layer is the worker side: the storage
handle, retry/backoff policy, the apalis handler, and the fault-injection
harness that end-to-end tests need.

Solution

• JobBackend<J> — worker-side handle over apalis's Jobs table, built once at
  startup, yielding the apalis Storage<J> for worker registration.
• work<J> apalis handler (production + test-support variants) that
  deserializes, logs, and runs perform against the injected Input.
• Retry policy: ExponentialBackoff (1s base, doubling, 30s cap) +
  RETRY_BACKOFF; FAIL_STOP_RECOVERY_TIMEOUT keeps a tripped circuit breaker
  open until a human-supervised restart.
• on_terminal_failure stops the worker and notifies the supervisor when
  retries exhaust; JobError models a failed or injected job.
• FailureInjector (test-support) arms a Job::KIND so the next instance fails
  terminally and sticks to that Label across retries while others run.
• build_poll_config tunes a 100ms poll interval with backoff for sub-second
  pickup.
• Test: the injector targets the first armed instance and spares others.

Closes RAI-915.

[coderabbitai]

Warning

Review limit reached

@0xgleb, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 59 minutes and 56 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 98398dae-299e-4fe9-9bb1-04997709787b

📥 Commits

Reviewing files that changed from the base of the PR and between fc40125 and 5516230.

📒 Files selected for processing (3)

• crates/event-sorcery/Cargo.toml
• crates/event-sorcery/src/job.rs
• crates/event-sorcery/src/lib.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/job-worker

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[0xgleb]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• adr: own the durable-job backend as an event-sourced apalis Backend #30
• adr: gradual consumer migration from services to jobs #19
• docs: migrate docs to the jobs model #20
• feat: migrate examples to the jobs model #16
• feat: replace EventSourced::Services with Jobs and wire atomic enqueue #15
• feat: add buffered JobQueue and apalis enqueue #14
• feat: add build_supervised_worker macro #13
• feat: job worker #12 👈 (View in Graphite)
• feat: add job module #11 : 1 other dependent PR (#31 )
• adr: jobs replace services #8
• master

---

How to use the Graphite Merge Queue

Add the label add-to-gt-merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has required the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[findolor]

Approved.