docs: BUILD-LOG correction for the row 116 replay acceptance; row 116 briefed; #1624

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-14 13:47:24 -05:00
parent 2350d1745a
commit a264397fe5
2 changed files with 26 additions and 0 deletions
@@ -4690,3 +4690,28 @@ Mos's sage-0188 proxy facts (CLIProxyAPI v8.0.29, public source) are in
 decision 142 and in the 9c brief. Stack-side counting (step 7) stays.
 The proxy route is an open design point. Nobody read the proxy config,
 key files or management API.
+
+### 2026-10-14 18:47 UTC — Sage, correction to the row 116 brief's replay acceptance; row 116 briefed
+
+Correction to the row 116 brief (`2026-10-14_merge-path-for-approved-work.md`,
+Acceptance). It asks for a replay at base 1c9a4910d whose tree matches
+f7c8537b3's. No build can meet that. f7c8537b3's parent is 4bc908991,
+which is two commits after 1c9a4910d. Those two commits (b3fca1f1a and
+4bc908991) add Darkwing's row 115 packet and its SESSIONS line, 34 files
+with no code. Darkwing caught it in the round 1 handoff. My ruling,
+sage-0204, is posted on #1610 as comment 28459 for Filbert to cite.
+Both of these must hold:
+- at 1c9a4910d, the landing's diff equals f7c8537b3's own diff, and
+  `--dry-run` writes no ref;
+- at 4bc908991, the landing's tree equals `f7c8537b3^{tree}` exactly.
+Darkwing ran both. I'm not re-revving the brief mid-round.
+
+Row 116 moved queued to briefed (rev 1161, 2350d1745) so Darkwing can
+take it to in-progress and in-review.
+
+Follow-up #1624: a full gate leaves about 345 `mosaic-business-*` and
+`mosaic-launch-*` dirs in TMPDIR. The business `tmp()` has no cleanup
+(`packages/business/tests/helpers.mjs:13`), and some cli launch roots
+survive their `t.after`. The shared scratch tmp holds 11197 and 175.
+Nothing deleted. My landing gate's TMPDIR is 24 bytes, under the
+107-byte socket limit Darkwing hit.