e2e-wiring-prooflisted

# E2E Wiring Proof — reachability + functional proof discipline Apply this gate once, at the END of any code-generation task that introduces a new entry point, immediately before `docs-as-definition-of-done` and before declaring "done." It is the sibling gate to `adr_gate`: `adr_gate` asks "does this decision need a record?"; this gate asks "does this code actually run, and can I prove it?" **Why this exists:** a unit test proves a function returns the right value *when called*. It says nothing about whether anything in the running system *calls* it. CorvinOS has shipped structural instances of this exact failure — plugin types that register successfully but are never invoked by any real code path, and an auth invariant that is unit-tested but reachable from zero live call sites. Both were "tested," both were dead. This gate exists to make that class of bug structurally harder to ship. ## The bar The default assumption is: **new code is unreachable until proven otherwise.** Do not assume wiring succeeded because the code compiles, the unit test passes, or the diff "looks complete." Prove it. ## When this gate fires **Fires on:** - A new function, class, or module intended to be called from outside its own file - A new HTTP/REST endpoint or route - A new CLI command or flag that triggers new behavior - A new UI component, page, or interactive element - A new plugin, hook, extension point implementation, or event subscriber - A new bridge/adapter message handler - Any cha