[JOsacky]

Operator recovery can enqueue repeated copies of an identical request, and FIFO lets replay batches delay fresh customer turns. Concurrent jobs in one Git worktree can also clean each other's uncommitted files at startup. Meter incident evidence is recorded in MeterApp/meter-repo issue 14998 comment 6156966412 and PR16219; PR16165 protects named-branch commits only.

This scoped runtime repair:

• Shares replay admission across HTTP and cloud: reuse identical queued/running payload+query work, including replay chains and retained jobs without fingerprints. Distinct source-message payloads remain separate, even in the same conversation. Completed jobs can be replayed again; application receipts remain authoritative. Existing in-flight dedupe opt-outs apply.
• Alternates eligible fresh and replay jobs, preserving FIFO within each class. Running work is never preempted; blocked jobs do not stall unrelated eligible work.
• Reserves canonical Git worktree roots exclusively by default, including jobs in subdirectories and across skills. Independent worktrees remain parallel. The new serialize_cwd setting enables exclusive non-Git directories or explicitly opts out for coordinated Git jobs. Reservations survive preparation, fallback, retries and cancellation until terminal completion.

Validation: seven new disposable subprocess/Git tests cover repeated recovery through both entry points, legacy binary jobs, separate turns, fresh work during replay batches, cross-skill/symlink/root-subdirectory ownership, independent worktrees, cancellation/failure release, and cwd changes during fallback. The fallback regression fails without its correction. Independent read-only review found no remaining correctness issues. At e9ab3fa, npm run check passed: strict types, all 340 tests across 47 files (47.32s), build, generated schemas and release metadata. Required hosted CI is pending.

No open runtime PR covers this work. Meter's broader shared-workspace migration PR15135 remains separate. The guard covers one daemon's queue, not external cleanup, another daemon or direct local processes. No runtime release/install or host adoption is performed by this source PR, and no customer reply or receipt is verified. No real jobs, live concurrency, access, credentials, webhooks or support/payment policies were changed.