Dashboard failure explanations

Verification Boundary

Static rendering separates absent dashboard service, actual failure and missing configuration. It does not mount the home page or exercise its attention and request hooks.

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

• Dashboard explanations separate three unavailable states.

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 imported functions, registry declarations and any static component rendering are real. Independent in-memory inputs represent grants, contexts or records; there is no deployed service or browser session.

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.