From 0f83559ecc5e08738f24118556ec1bd82fb939df Mon Sep 17 00:00:00 2001 From: kami Date: Fri, 28 Aug 2026 23:45:03 +0400 Subject: [PATCH] Record F18, the merge, and what run 12 leaves open Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01CVbaKucEYBjMqVeUgJUsc1 --- BURNIN.md | 57 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 57 insertions(+) diff --git a/BURNIN.md b/BURNIN.md index 7890df2..8059448 100644 --- a/BURNIN.md +++ b/BURNIN.md @@ -2274,3 +2274,60 @@ tmux -L orchestra kill-session -t Task `06G4JX6MSQEP7N0D5JWW9EP5X4` is the other run 12 task and is `in_review` on a pull request. It is real work and should be reviewed or failed, not cleaned. + +### F18 closed: a bounded observation ring + +`d6ee10f`. `WorkerHealth` now carries up to sixteen distinct observations, each +with a repeat count and first/last times. Collapsing is by message, not by +position, because a loop interleaved with other failures would otherwise still +flush the ring. Eviction drops the least recently seen, so a loop keeps its +slot but carries the count that says what it is. `last_error` and `error_at` +keep their wire names and still report only the newest failure. + +The ring lives in memory beside `last_error` and is not persisted, which is +what `last_error` already did across a restart. + +Deployed and verified on both halves. It reports nothing yet, because +`omitempty` hides an empty ring and nothing has failed since the deploy. No UI +renders it: `internal/ui` never showed `last_error` either, so +`GET /v1/federation/workers` is the only reader today. + +### Run 12 closed out + +PR 17 merged, task `06G4JX6MSQEP7N0D5JWW9EP5X4` completed at v32, pane closed +by the normal completion path. The quality gate was re-run independently +against the submitted commit `419e17fc` before the merge, rather than trusted +from the worker's own report: + +```text +bash -n scripts/*.sh syntax ok +bash scripts/orchestra_e2e_healthcheck.sh OK - all healthchecks passed, exit 0 +bash scripts/test_healthcheck.sh all checks passed, exit 0 +``` + +Worker state is empty: no sessions, no leases, no release transactions, and +`tmux -L orchestra ls` lists nothing. The two panes the previous section left +for an operator were already gone by then. + +| Half | Revision | +|---|---| +| Coordinator, homesrv container | `d6ee10f` | +| Worker, workpc systemd | `d6ee10f` | + +```text +commit d6ee10f02843e2267c859b03d17db00995941e64 +coordinator sha256 f8a847477ae0ac03fe78338775f52ed1f167f0e67eab557feffe4d67da3ad99e +worker sha256 fe7d2188b12369fb7682d3424fa11e2db47abed9c55313291a4b467b5972d02d +``` + +### Still open after run 12 + +- **29 blocked `test-e2e` tasks**, mostly burn-in debris. Operator hygiene, not + lifecycle code. +- **Three queued `correx` tasks** that cannot be scheduled, because `correx` has + no entry in the coordinator's `config.jsonc`. Either give it one or block them + explicitly. +- **Gitea returns 422 for a review on your own pull request**, so + `REQUEST_CHANGES` needs a separate bot account for `ORCHESTRA_GITEA_TOKEN`. +- **A blocked task that is never reopened can still loop** on a dead release + transaction. F59 covers failed, not blocked.