faffter-noon-concurrency-sequential

Use the sequential concurrency executor, which dispatches one build subagent at a time in the foreground and blocks until its terminal token returns. Each merge sees main exactly as the prior merge left it, so no rebase step or race handling is needed.

The sequential executor is the zero-config default that builds one issue at a time with no worktree contention. The parallel alternative (faffter-dark-concurrency-parallel) runs independents concurrently for speed but must honor the same seven slot-contract obligations.

A missing token triggers ground-truth reconciliation rather than a blind park. The orchestrator reads the run directory artifacts and git state (PR, CI, merge status) and records the terminal outcome to the run ledger itself.

On a tamper (exit 1) or unavailable verification (exit 2), the executor runs the shared park procedure for that unit and does not reconcile its run-dir evidence. Evidence mismatches on the per-issue AC or review files trigger the same unit-scoped park.

Yes. Optional matchers route the build model by retained confidence or by tier, resolved per issue at dispatch. A collision chain resolves to its most-demanding member so no chained member is under-served by a cheaper model.

Avoid it when throughput matters more than simplicity and your project can absorb concurrent worktrees. In that case swap the concurrency slot to the parallel executor, which still honors the same merge-gate and custody obligations.