From 48326d4301b70f3e2baf0d40f74f572cbdacc0ab Mon Sep 17 00:00:00 2001 From: kami Date: Fri, 28 Aug 2026 01:24:22 +0400 Subject: [PATCH] Record F33, the launch that confirmed itself in seven milliseconds Run 5's first attempt never started: ConfirmInput's first poll beat the TUI's render, saw an empty editor and called it editor_cleared. The prompt sat unsent while the lease renewed against a pane doing nothing. Recovery is left to lease expiry rather than a keystroke, so the relaunch stays autonomous evidence. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_011xsXyr5J1RACo71YeKG3Pu --- BURNIN.md | 57 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 57 insertions(+) diff --git a/BURNIN.md b/BURNIN.md index 7cc8ede..91006e9 100644 --- a/BURNIN.md +++ b/BURNIN.md @@ -1425,3 +1425,60 @@ F30 fixed in 2dc90bd, DEPLOYED, partially live-proven, rest blocked by F32 F31 fixed in 6523002, DEPLOYED, awaiting run 5's first rotation F32 fixed in 92adf04, needs a rebuild, BLOCKS leasing on workpc-claude ``` + +## Run 5, first attempt: the launch never went off, 2026-08-28 + +Filed as `kami/test-e2e#5`, ingested as `06G4A4F0TFXKZHJE48N05XN1HG`, placed on +`workpc-claude` by normal routing. Issue filed to confirmed launch: 44 seconds. + +Then nothing moved for seven minutes. The pane held the launch text unsent: + +```text +❯ @.orchestra/launch.md is your complete Orchestra launch instruction. Read + .orchestra/launch.md now and follow it. + +0 tokens ⏱️ 0m 0s session ... - none +``` + +### F33: an editor that never rendered confirmed the submit + +```text +first_submit_at 21:13:19.570302125Z +confirmed_at 21:13:19.577191672Z +confirmation editor_cleared submit_attempts=1 +``` + +Seven milliseconds. `ConfirmInput`'s first poll ran before the TUI rendered the +pasted text, found an empty editor, fell through to the idle branch, and called +that proof of submission. + +The two launches that worked earlier took `submit_attempts=2` over roughly +500ms. The difference between a good launch and this one was scheduling luck, +which is why it had never been seen before. + +The cost is worse than a failed launch. The coordinator believes the agent is +working, so the lease renews against a pane that will never produce anything, +and the failure only surfaces at expiry half an hour later. + +Fixed in `32220d9`. An empty editor counts as proof only after it has held the +text, or after it has stayed empty past a settle window. Text seen and then +gone still confirms immediately, and so do `busy`, `blocked` and `queued`. With +the fix the failing case reaches the existing resubmit path instead: the text +appears, is recognised as unsubmitted, and Enter is resent. + +### Recovery, deliberately not by hand + +Pressing Enter in the pane would fix this run and prove nothing. The lease is +left to expire and relaunch on its own, which is the autonomous path run 3 +already proved. The worker carrying `32220d9` is deployed first, so the +relaunch uses the fixed confirmation. + +### Ledger + +``` +F29 DEPLOYED, live-proven +F30 DEPLOYED, live-proven +F31 DEPLOYED, still awaiting a first rotation +F32 DEPLOYED, live-proven, slot reaped and freed +F33 fixed in 32220d9, needs a rebuild, BLOCKS every launch nondeterministically +```