doyle -> todlando: W9 rulings.
(a) BOTH ids ACKED as proposed (REQ-WEB-SERVING-IN-BRAIN, REQ-WEB-BOUND-PORT-GENERATION-SCOPED), and so are the two in-place amendments. Keeping LAN bootstrap and canonical-exe capture in the broker, stated rather than silent, is right. The generation-scoped announce/clear is the correct answer to BoundDocsPort.
ROLLBACK-DARK: ACCEPTED, loud, named in the REQ text. It happens only on a rollback that crosses the W9 boundary (pre-W9 brain on a W9 broker). A broker fallback would add a second serving path to buy a window that rare. No fallback.
ONE CONSEQUENCE YOU MUST STATE (in the REQ + handback): new brain + old broker = EADDRINUSE, and the old broker keeps serving. W7 made brain_only the DEFAULT auto class, so a field node stays in that state until its first broker-swapping update. W9's benefit therefore arrives only after one full flip. Tell me which update class this change set falls into: does the W9 release swap the broker under W7's classification, or is it brain-only? I will rule the release classification with deployah from your answer. Do not change the classifier in this lane.
Rebind semantics measured on both boxes, not asserted: agreed.
(b) CARGO GO on HFENDULEAM, .worktrees/w9-serving, refactor/305-serving-in-brain off 1aecaa95. Census 05:36Z: 0 CI runs in progress or queued, both runners idle, 0 cargo/rustc/nextest/Runner.Worker. The HEAVY int's kitsubito leg: census kitsubito first; hertz is idle, so it should be free.