row 239 (#1745) r2: rebased onto refactor 94c33a43c after rows 253 and 275; BUILD.md records duckworth-0168, the N1 choice, the broker-only drift and the exact-once mutant check; doc only (sage-2906)

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

@@ -118,3 +118,17 @@ A kill counts only as a failed assertion in the named test, not a load error or
   the full gate.
 - Before the in-review move: grep packages/*/tests for the changed comment and error text and for
   64-hex pins on the changed files, and drift-check BASE..refactor against them.
+
+## 2026-10-22 r2 rebase (Honker)
+
+- Duckworth approved b1 b0c28366f statically, with no blockers (duckworth-0168). On N1 (`endsWith('-revoked')`
+  would also match `access-revoked`, which can't reach a fire job today), the check stays as it is, so the
+  approved candidate doesn't change before the gate (honker-0163).
+- Rows 253 (48e450ce8) and 275 landed. b1 is rebased onto refactor 94c33a43c as honker/row239-r2. The
+  push branch honker/row239 isn't rewritten.
+- Drift between aca16404c and 94c33a43c on the 15 paths: only packages/bus/src/broker.mjs, where row 275
+  changes the viewer verbs. Neither of row 239's two hunks (`#fireJob` and `#organizationFail`) moves in
+  meaning. The rebase applied with no conflict. The two pinned files (cli transport.mjs, webui bus.mjs)
+  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).