Date: 2026-08-21 UTC
The semantic front/back humanoid equipment layout is deployed in EventHorizon image sha-c5fbfae7c007. Both replicas are ready with zero restarts; /healthz and /readyz are healthy; the publicly served stylesheet contains .equipment-body-layout. Gitea Actions run 3001 completed successfully after performing exact-image, public-asset, health, readiness, and Android release verification.
AutoCoder backend and frontend are deployed from sha-0b9bcd34ec48. Action run 1023 passed frontend Rust/WASM checks, backend and frontend image builds, both rollouts, documentation sync, and cron deployment.
- The inventory implementation had merged, but EventHorizon deployment stopped on a pre-existing formatting failure.
- AutoCoder treated worker/branch completion as requirement completion without requiring exact branch checks, merge, deployment, immutable image, or live evidence.
- Gitea package storage accumulated untagged OCI manifests until the queue could not write, disabling post-receive action scheduling.
- Six working Gitea runners were removed after an AutoCoder runner library and unit tests were incorrectly treated as a live replacement. No production component invoked that library.
- AutoCoder branch validation did not compile its WASM frontend.
- EventHorizon's first production verifier used Kubernetes pod exec, although the CI service account correctly lacked that privilege.
- Reproducible Cargo targets on the Kubernetes host consumed enough local disk that pulling a new AutoCoder image triggered DiskPressure and pod eviction.
- AutoCoder requirement completion now waits for an exact branch revision, non-empty tests/builds, PR merge, exact merged workflow, applicable immutable deployment, and live acceptance evidence. The implementing worker cannot mark terminal completion.
- AutoCoder branch validation now compiles the WASM frontend; the missing frontend import found by that build was fixed.
- EventHorizon has exact branch validation and verifies the public stylesheet rather than using privileged pod exec.
- Gitea cleanup protects every live image and a bounded release history, deletes only unreferenced OCI manifests, and runs supported package blob reclamation hourly.
- Gitea package storage fell from 156.9 GiB to 71.5 GiB, reclaiming 85.4 GiB. Queue writes and post-receive scheduling recovered.
- The six proven runners were restored. REQ-0085 was returned to implementation-ready; they remain authoritative until a real AutoCoder-owned execution path passes representative live workflows.
- Runner registration directories are recreated safely; runner scratch remains on the worker NVMe.
- 55.5 GiB of reproducible local Cargo build artifacts were removed. Host DiskPressure cleared and root filesystem headroom recovered to 85 GiB.
- Obsolete EventHorizon PR 394 was closed after the safer public-surface verifier merged.
- EventHorizon PRs 393 and 395
- AutoCoder PRs 2591, 2592, and 2593
- EventHorizon main run 3001 and frontend run 3002
- AutoCoder main run 1023
Do not retire the baseline runners or mark their replacement complete until the replacement is connected to the live action intake, scheduling, execution, audit, and result path and exact-revision workflows have completed on it. Keep runner registration credentials in the Kubernetes Secret only; use the internal Gitea service URL for registration and never publish the registration token.