On 2026-09-07, the user authorized delivery of the investigated feedback-path repair. Product design and implementation documentation remains in the AutoCoder-Engine repository.
PR 3392 merged as 9edc406a917cefe97207c25faedc4c76ac5019e2. Required branch validation passed, including Rust tests, isolated PostgreSQL lifecycle tests, and release backend/WebAssembly builds. The normal repository-managed production pipeline completed successfully; no ad-hoc deployment configuration or database writes were used.
Namespace: autocoder-engine. Backend image changed from gitea.app.lan/autocoder/autocoder-engine:sha-3bf346a666f0 to gitea.app.lan/autocoder/autocoder-engine:sha-9edc406a917c. At approximately 08:37 UTC, backend readiness was 1/1 with zero restarts and /healthz returned ok. Five detached workers were Ready on the new image. The sixth retained the previous image while explicitly draining an unrelated existing merge-recovery task; application reconciliation replaces it after that task finishes. Frontend was unchanged because this rollout did not require a frontend image.
Application startup reconciliation corrected 35 feedback cases marked resolved without availability verification; the unsupported-resolved count became zero. EventHorizon cycle 77520 moved from delivery_blocked with integration ownership to failed without integration ownership, preserving its failure evidence. The accepted combined chat feedback report 37627 entered planning cycle 90644; its worker was running on the new image. This verifies restored intake-to-execution progress, not completion of the EventHorizon UI change or retrospective validation of all historical verified cases.
The busy worker was not interrupted. The reported EventHorizon chat behavior remains subject to managed implementation and independent production acceptance. Temporary local database tests used isolated disposable storage and were removed. Rollback uses the repository deployment workflow and the previous immutable image; the corrected case evidence must not be rewritten as a rollback shortcut.
The final draining worker subsequently refreshed through normal application reconciliation. All six detached workers were confirmed Ready on sha-9edc406a917c; no task interruption was required. The isolated test worktree and its build outputs were removed, and the pre-existing parent worktree requirements change was preserved.