Date: 2026-07-29
Commit: adc2d345bb57fce83538032531ed28246463ba47
Image: gitea.app.lan/eventhorizon/eventhorizon:sha-adc2d345bb57
Recent Persona Editor telemetry showed a multi-step tool turn growing to 733,085 request characters and failing with provider HTTP 400. Each successful field operation had appended another complete persona snapshot to the internal model transcript. The conversational Item Editor shared the unbounded snapshot pattern and also lacked the Persona Editor recovery path for unambiguous textual tool-call output.
- Both staged editor agents compact superseded successful draft snapshots while retaining the newest authoritative draft and structured errors.
- Four consecutive no-progress tool steps end in a no-tools summary instead of continuing indefinitely.
- The Item Editor now recovers supported wrapper, tagged, and prose tool-call variants and applies mutations to a candidate draft transactionally.
- Both browser editors capture readonly state at submission and refuse to overwrite a draft changed locally while inference was running.
- Persona and item saves remain explicit user actions; editor agents do not persist drafts.
- Rust formatting passed.
- Workspace tests passed: 376 backend and 11 frontend tests.
- Release backend and WASM frontend builds passed; WASM bindings generated successfully.
- Independent frontend workflow completed successfully.
- Kubernetes rollout completed with two ready replicas, zero restarts, and the expected image.
/healthz and /readyz passed on both pod addresses.- No synthetic production editor mutation was submitted; the next real editor interaction is the gameplay-level acceptance check.
Clippy was not run because the component is not installed on the host.
Revert merge commit adc2d345 through the normal repository workflow and allow the main-branch deployment pipeline to restore the prior image. Do not mutate the live Deployment image directly.