Invariant 3 says every capability is reachable with no plugin host present, but the build chapter says a host session always drives the loop and the no-host path is not built

Invariant 3 says every capability is reachable with no plugin host present, but the build chapter says a host session always drives the loop and the no-host path is not built

A premise contradiction (severity minor) found by the cross-document consistency pass.

• End A: .abcd/development/brief/02-constraints/03-invariants.md:13 — "every capability is reachable with no plugin host present"
• End B: .abcd/development/brief/04-surfaces/34-build.md:537 — "A host session always drives this: the no-host path, where a host-routed role goes to the machine's runner.fallback_host, is the process driver's reversal of the host-delegated boundary, and waits on the ADR decision 6 of the intent owes."

Invariant 3 is a non-negotiable rule: every capability is reachable from the CLI with no plugin host present. The build chapter says a host session always drives the loop, and that the no-host path, where host-routed roles fall to a machine runner, waits on an unwritten ADR. So the build capability, as described, cannot be reached without a host, which the invariant rules out.

Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 76.