row 264a r10 (#1769): rebase on landed 281 (e479521d3), all 16 =; broker.mjs overlap read; cli limit 1800 s from 281's 591 s run (sage-2665, sage-2668, sage-2647)

agents/gizmoduck/work/queue-264/BUILD.md

@@ -396,6 +396,27 @@ range-diff is `=` for all fifteen.
   held sessions lists twice, five keys kept) show as two rows. 278's three webui tests use fake bus
   objects and never reach the broker's query.
 
+### Round 10 on landed 281 (e479521d3)
+
+Row 281 (a fire or delete revokes the instance's grants) landed, and refactor moved from 385a7194c
+to e479521d3, fast-forward (sage-2668). r9's 16 commits moved by rebase with no conflict, and the
+range-diff gives all 16 `=`. The r9 run never started (sage-2665), so no result carries over.
+
+- 281's paths over 385a7194c: packages/bus/src/broker.mjs, five tests (bus fire-revokes-grants,
+  gitea-grant, grant-executor, lifecycle-revoke; cli lifecycle) and its own packet. The one shared
+  path is broker.mjs, and the hunks don't touch: 264a's at :128, :455-:1081 and :3276-:5537, 281's at
+  :396-:400 and :1273-:3831 (base lines).
+- 264a removes #routeThread, #threadFor and #threadHolder. No line 281 adds calls them, and every
+  private name the merged broker calls is defined. No line 281 adds names thread_claims,
+  thread_opens, sessions or session_defaults; its section 3a "claim" is the host-key claim.
+- 281's tests name no schema version, migration, sqlite_sequence, thread_claims or 64-hex pin. cli
+  lifecycle.test's `sessions` are launcher.registry.sessions, which 264a doesn't change.
+- No 264a test reads a 281 path as text or pins its hash. The touched tests that import broker.mjs
+  run against the merged file in this round's gate, which is the test of the pair.
+- 281's gate (its BUILD.md, "Whole packages") recorded the cli suite at 591 s, longer than the 535 s
+  the table used. 3x is 1773 s, so the cli limit goes from 1650 s to 1800 s. Its other times (bus 23 s,
+  each scripts/test-*.sh at most 36 s) are under the table's, and those limits stand.
+
 ### Run limits (sage-2634, sage-2637, sage-2647, mos-1275)
 
 Every run in run-264 goes through `timeout -k 10 LIMIT`, so a hang stops the run instead of holding
@@ -411,7 +432,7 @@ red, and goes to Sage first (sage-2637). A timeout in the shell phase goes to Mo
 | stack-release.test alone | 505 s | row 234 r3 singles with mutants, 2026-10-21 (plain r3: 482 s) | 1600 s |
 | each other touched file alone | 15 s (thread-launch.test); end-launch, gitea-migration, message-filter, sessions, thread-claims, thread-cli and chat have none | rows 234, 235, 210 logs | 300 s |
 | bus suite | 23 s | row 235 run 1b; row 278 run 3: 22.5 s | 900 s |
-| cli suite | 535 s | row 235 run 1, 2026-10-21 (Megavolt row 199: 472 s) | 1650 s |
+| cli suite | 591 s | row 281's gate, 2026-10-22 (row 235 run 1: 535 s; Megavolt row 199: 472 s) | 1800 s |
 | webui suite | 57 s | row 278 run 3 (row 66 r2: about 60 s) | 600 s |
 | each scripts/test-*.sh | 42 s (test-foundation); task 36.8, queue 23.4, land-work 12.6, release 12.2, discord 8.8, conductor 8.1, config 3.2, extension-package 3.0, auth 1.9 | the longest of row 268's gate (2026-10-22 04:40Z), row 196's receipts and row 278 run 3 | 900 s |
 | mutant probes M1-M4 (sessions.test, thread-claims.test) | none recorded | | 300 s |