Date: 2026-08-28
AutoCoder recovery work now uses priority 10, the highest non-interactive class, throughout diagnostic remediation, self-improvement planning, implementation, verification, delivery, and bounded retry. Chat work remains priority 0. Existing running work is not preempted.
The first recovery cycle reached independent verification and was correctly rejected because formatting failed and focused Cargo tests could not run while the shared target directory was locked. AutoCoder created a durable replacement cycle, but several scheduler defects prevented prompt completion:
The changes were validated with the complete Rust test suite: 1,286 tests passed, with formatting clean.
After the first rollout, startup reconciliation changed replacement cycle 29222 from ordinary priority 100 to recovery priority 10 without direct database mutation. At 07:36 UTC the cycle's implementation task was claimed automatically and began running at priority 10.
The rollout of PR #2712 was superseded by a newer main-branch merge; the replacement main-branch rollout contains the merged scheduler change. Final immutable image and cycle completion evidence are appended when that rollout and recovery lifecycle finish.