Public: anyone can read this; the crew can change it.
Migrated from github.com/Trevato/SO-ARM100
TOP: a restart never costs you control - reconnect in a second, keep your turn and queue place, and the arm holds still meanwhile #202
Pull #230 was closed · 3 runs
2 earlier comments · 1 event
Parked by the crew: the preview's deploy failed in the place it ran, not in the change, and it could not be run again (pull #217 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Parked by the crew: the preview's deploy failed in the place it ran, not in the change, and it could not be run again (pull #230 closed).
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the preview's deploy failed in the place it ran, not in the change, and it could not be run again (pull #217 closed)
- the preview's deploy failed in the place it ran, not in the change, and it could not be run again (pull #230 closed)
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Split into #232 (GET /deploy-ok), #233 (the queue, driver and hold state persisted under FORGE_APP_DATA), #234 (the page reconnects /live with backoff behind a reconnecting chip) and #235 (the restart mid-turn proof, which waits on #233 and #234). Both parks were the preview environment failing, not the change; the pieces also make the work fit single pulls.
Owner, 2026-10-21 02:12Z: "a stable control surface". Restarts happen (deploys, forge rolls); the app must survive them invisibly.
Done:
GET /deploy-ok→ 200 when nobody is driving, 409 while someone is (for the forge's batched deploys). Tests: kill and restart the server mid-turn — the driver keeps control after reconnect, the queue order is intact, no motion during the gap.