From 848ceb68a4503c6f267ecb42b43941f1b28f7302 Mon Sep 17 00:00:00 2001 From: Jason Woltje Date: Tue, 13 Oct 2026 19:02:17 -0500 Subject: [PATCH] docs: row 111 landing note, Dewey note a recorded for the next host.mjs row (#1605) Co-Authored-By: Claude Opus 5.5 --- docs/plans/2026-10-13_landing-follow-ups.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/plans/2026-10-13_landing-follow-ups.md b/docs/plans/2026-10-13_landing-follow-ups.md index 19c939e10..0968e7bd1 100644 --- a/docs/plans/2026-10-13_landing-follow-ups.md +++ b/docs/plans/2026-10-13_landing-follow-ups.md @@ -302,3 +302,13 @@ Dewey approves on the row's issue, naming the candidate manifest, and the suites above pass on Sage's gate rerun. Decision 109 notices go to Mos before and after landing. It goes live only with a new copy, a re-pin and a bus restart under Mos's go. + +### Landed (Sage, 2026-10-13) + +Row 111 landed as 9774d70db (#1605 comment 28342, issue closed). Dewey's +approve (comment 28331) carries note a for the next row that touches +`host.mjs`. `ended()` waits with `events.once`, which rejects when the +child emits `error`, so that path skips `release()`. A follow-up row +that changes `startHost` or `ended()` fixes it with a test. Note b (an +orphan child when `fork` throws) occurs only in the tests and needs no +row.