An operator discussion queued as superproject-chat-1790595653433692762 for SuperProject gitea:AutoCoder but did not start during the global automation pause. The manual operator lane admitted only AutoCoder-Engine repository chat kinds. The SuperProject discussion is a separate task kind, superproject-discuss.
PR #6746 merged into dev as b59787a722d7f906d1eff78bedbe739cc738c860; branch validation and candidate run #3937 succeeded. The existing automatic main delivery integrated that tree in PR #6747, and production promotion run #3939 succeeded. The documented publish-worker-image.yaml workflow was dispatched on main for exact source revision b59787a722d7f906d1eff78bedbe739cc738c860. It selected worker image gitea.app.lan/autocoder/autocoder-engine@sha256:45b592ca390969e632cb5fa3490c7c1247c9a2133a6d81f1b4873dc29227460a, replacing digest sha256:060932b720ca1b2826556fea4fb5a16b346432258cadd49269046c3fb01a4ab9. All three scoped operator worker pods reached Running on the new digest on drg-k8s-worker-01.auth.home.lan; backend rollout was ready.
The paused lane now admits only authenticated operator discuss tasks for SuperProject gitea:AutoCoder in addition to the existing canonical repository chat kinds. The AutoCoder SuperProject chat actions route through Codex App Server; discussion requests the built-in read-only permission profile. Other SuperProjects retain codex exec. No general implementation or background worker lane was enabled.
The preserved task was claimed by autocoder-agent-operator-chat-70ccf7f78b4fd399705fdd92a7850e00 at 12:05:28 UTC and completed at 12:05:47 UTC with exit status 0. Its recorded protocol contains App Server thread/started and turn/started events. A normal authenticated SuperProject chat session request returned the linked completed assistant response. The production configuration still reported AUTOCODER_BACKGROUND_AUTOMATION_ENABLED=false, AUTOCODER_IMPLEMENTATION_WORKERS_ENABLED=false, AUTOCODER_REQUIREMENTS_AUTOMATION_ENABLED=false, and AUTOCODER_OPERATOR_CHAT_WORKERS_ENABLED=true.
The worker image setting was changed through the repository workflow with its migration Lease and rollback trap. If this release must be reverted, restore the prior immutable worker digest through that governed worker rotation path after confirming no active chat task would be interrupted. Preserve the chat task and session history.