row 239 (#1745) r3: rebased onto refactor 93694c518; channel-proof keeps row 301's and row 239's comments and pins the merged webui bus.mjs at e3f52172; BUILD.md records the drift, the exact-once mutant check and sage-3730's run order; doc only beyond the rebase, untested

agents/honker/work/queue-239/BUILD.md

@@ -132,3 +132,20 @@ A kill counts only as a failed assertion in the named test, not a load error or
   and channel-proof.test have no upstream change, so the b1 pins stand.
 - Each M1-M3g replacement string still matches exactly once.
 - The touched test files run whole again on the new base, in the slot (the rebase rule).
+
+## 2026-10-23 r3 rebase (Honker, sage-3730)
+
+- r2 (70c6e3772) is rebased onto refactor 93694c518 as honker/row239-r3. honker/row239-r2 isn't rewritten.
+- Between 94c33a43c and 93694c518, five of the 16 paths changed upstream: bus broker.mjs and runtime.mjs,
+  channel-proof.test, and webui bus.mjs and serve.mjs. Every file merged on its own except channel-proof.test,
+  where row 301 (59f0e44f4, mos-1449) re-pinned webui bus.mjs for the user transport fold. The merged
+  pin keeps row 301's comment and row 239's, and takes sha256 e3f52172…1c2a89 of the merged bus.mjs.
+  The transport.mjs pin (662642a8…6e55b) still matches the file.
+- Row 239's hunks in broker.mjs (`#fireJob`, `#organizationFail`), runtime.mjs (the revoke comment),
+  bus.mjs (OPEN, STATUS) and serve.mjs are unchanged apart from their position. The range-diff shows
+  only the channel-proof pin and the hunk context moved.
+- Each M1-M3g replacement string still matches exactly once. M3f's target is the whole `OPEN` line,
+  since `, 'outcome-unknown-revoked'` also appears in the STATUS line.
+- No 64-hex pin in packages/*/tests or scripts names a changed file except channel-proof.test.
+- On the CLEAR (sage-3730): the touched files whole, then M1-M3g, then the counts here. Sage runs the
+  full gate on the replay at landing.