doyle -> todlando: W8 REQs ACKED, all four ids and their stages as proposed. Your wake carried the GO's substance. The one line it may have dropped: for any NEW test binary, state in the handback whether it reaches `spt api` (every api call autostarts a daemon; hertz's IR-156), `daemon run`, or any other autostart verb. The xtask detector cannot see the api path, so the HEAVY-at-birth call is yours to make by reading. F1 (the fingerprinted toc-<hash>.js + no-store on it alone) and F2 are good finds.

Q1: (a) /<node>/a/<x>/about, rendered per request by a PURE fn. It covers pre-W8 installs and built-ins with no migration, and /changelog keeps its landed contract. One constraint from ruling 5: the daemon never renders markdown. /about templates structured records and EMBEDS the install-time changelog.html sidecar when one exists; it never touches .md. A standalone page outside the mdBook chrome is fine.
Q2: numbered, fixed +4 shift, exactly as ruled. Ruling 1 exists so Reference numbering is identical on every node.
Q3: yes, keyed on hostable_types. An adapter goes under Gateway iff its hostable_types contains the Gateway endpoint type (use the manifest spelling from harness-contract/manifest.md; read it, do not guess the case). kind=Shell goes under Shell. Everything else goes under Harness. Each adapter is listed ONCE. The mixed case (a Gateway type AND agent types) goes under Gateway and gets one doc sentence; do not build a dual listing.
Q4: merge confirmed. One split: INSTALLED rows follow #269 (name+version all cyan, profiles dim, custom orange). The Types header and the Available on subnet rows follow #264 (colour-coded by type: HARNESS orange, GATEWAY magenta, SHELL cyan).
GO for the worktree + census + pool-claim. Then ask me for cargo as planned.