Recorded 2026-10-07. Authorized outcome: operators can right-click any AutoCoder UI element, choose Feedback, and durably record feedback about AutoCoder-Engine itself.
edc0507eed710a2aaa83f06bebf2dcc0a5c1d97f; development merge/source: e34a19315848e0f15efed5480230569bf164a755.9ebf0a5c6451c29a09a116646aa5347ebc3ba20f; verified source tree equals development.e34a19315848e0f15efed5480230569bf164a755-4356-1 is production_live. Retained validation evidence reports unit, database, native and WASM checks passing.gitea:AutoCoder release controls allowed TEST delivery and reviewed_main_automatic production under REQ-0157/operator-direct-main-20260926; no stop or permission control was changed.autocoder-test and autocoder-engine serving deployments with the same immutable artifacts. Backend: sha256:131db342e13cdee2dcd7bfc83c40dbdde8904952bb69a67d04a3c99bf807251c. Frontend: sha256:0be376eee7739399432e216143841e481477b8bee10f5c92ac533c042071a8a9./healthz revision headers and /pkg/build-revision.txt report the development source above; served feedback JavaScript matches the source hash. Backend availability was briefly transitional during promotion and healthy by acceptance.Worker-host Chromium used the real deployed interface, authenticated through the supported operator API identity. The right-click menu and multiline form worked in TEST and production, including production main, Graph, Issues and Settings routes. Shift+F10 and a 360-pixel viewport passed.
The form saved the clearly marked Codex acceptance note as production feedback 43821, targeting AutoCoder/AutoCoder-Engine. Retrying the identical submission returned the same receipt. A read-only PostgreSQL check confirmed one receipt, one feedback case, one occurrence and one evidence entry, with the source revision and structural element context retained. Submission created no approval provenance. Anonymous requests returned 401 and an unexpected element value field returned 422. Browser page errors: none.
The production acceptance note is retained as verification evidence and explicitly says it is an agent record, not an operator product request. No product issue or lifecycle decision was authored during acceptance. Task-scoped browser data is cleaned up.
Refresh the application, right-click an element, choose Feedback, enter the note and select Save feedback. Shift+right-click opens the browser context menu. The form preserves an uncertain submission for retry and confirms persistence with its receipt ID. Target field values, surrounding DOM content, HTML and URL queries are not automatically collected.
Feedback reuses the existing PostgreSQL receipt/case store and governed intake. No database migration or permission expansion was required. Prior immutable releases and release receipts remain available through the existing recovery lifecycle.