Static console route guards

Verification Boundary

Filesystem scans compare page inventory and canonical route declarations, naming conventions and forbidden literal console paths. Source conformance does not establish runtime routing or every page’s guard.

This register records static review at the supplied source commits. The suite exists, but this pass does not run it or mark its conformance verified.

What This Suite Proves

• Source guards keep the page inventory within the address boundary.
• Defined address words follow the naming convention.

Bindings that span files are collective: each file contributes only its recorded assertions. The exact anchors are in frontmatter.

What It Does Not Prove

The register claims only the linked scenario outcomes at this boundary. It establishes no passing deployment result, complete permission matrix or unlisted cross-capability journey. Proposed scenarios and the remaining lifecycle, invariant and race obligations stay in the coverage findings.

Real Dependencies and Test Doubles

The suite reads actual pinned source files and route or redirect declarations. It uses local assertion helpers; any limited redirect matcher is a test model rather than a running server.

Must Not Be Doubled

Do not replace the function, component, registry or source declaration under test. Keep the expected outcome independent of its implementation; injected inputs do not justify stubbing the computation being verified.