Date: 2026-08-27 UTC
AutoCoder-Engine PR #2704 was merged as 43c42eed9d261cc5393fe981cb4f5ea5999a7cca and deployed by Gitea Actions run 1356.
- Repository chat now selects one open
waiting_for_user issue at a time by urgent, important, then oldest order and asks one contextual question.
- The operator's next answer is attributed, persisted idempotently, and handed to the existing governed feedback lifecycle.
- Explicit natural-language create, comment, update, close, and cancel requests are interpreted into a typed action, server-authorized, applied once, and audited.
- The Issues workspace is read-only audit/history; mutation controls were removed.
- Backend image:
gitea.app.lan/autocoder/autocoder-engine:sha-43c42eed9d26
- Frontend image:
gitea.app.lan/autocoder/autocoder-engine-frontend:sha-43c42eed9d26
- Both deployments reached Ready with zero restarts.
- Startup migration added
codecartography_chat_issue_actions, codecartography_chat_issue_answers, and focused-issue fields on codecartography_chat_sessions.
- 1,284 Rust tests passed.
- Release hydrate build for
wasm32-unknown-unknown passed.
- An authenticated live chat load selected urgent issue #8 and queued exactly one inquiry; a second load reused the same focused issue and task without duplication.
- The worker completed and backend reconciliation persisted the contextual question and changed the focus to
awaiting_answer without browser polling.
Rollback uses the prior immutable backend and frontend images. The additive database objects are safe to retain during rollback; do not drop them during an incident.