Date: 2026-08-30
Service: AutoCoder Engine
Repository: AutoCoder/AutoCoder-Engine
AutoCoder now persists objective-progress time and cumulative effective-token baselines across every requirements-goal segment and resumption. Authoritative goal.tokensUsed and thread/tokenUsage/updated cumulative counters are delta-accounted, so resumed segments cannot reset stagnation accounting or count the same provider usage twice.
A long-running command with no provider-token growth remains exempt. An unchanged objective may be recovered once on the same governed task, thread, workspace, and usage record; the next unchanged stall becomes the visible terminal state failed-objective-stagnation.
3b6a0f1d712a20741625ed66676712354ce7cab8b23246fee88839c8gitea.app.lan/autocoder/autocoder-engine:sha-1625ed666767/healthz returned "ok"Independent verification passed cargo fmt --all -- --check, the 13 focused REQ-0121/REQ-0122 tests, and the complete locked lib/bin suite (1,409 tests, zero failures).
Task requirements-1788059495213746436 had reached two ordinary budget checkpoints and 241,484 effective tokens on the prior worker image without an objective repository change. The old worker was allowed to finish its active Rust compile and checkpoint; it was then replaced automatically by a worker running sha-1625ed666767.
The new worker reclaimed the same task, thread, workspace, and cumulative usage record:
failed-objective-stagnation;This proves cross-segment accounting, one bounded recovery, terminal escalation, worker-image replacement, and the governed self-improvement path in the live environment.
During diagnosis, two known looping requirement tasks were cancelled with exact task/thread/state guards to stop further provider waste. Fresh ordinary requirement attempts that raced ahead of the priority repair were superseded only before or at their first checkpoint. No account credential or quota state was modified.