Demonstration console addresses
Verification Boundary
The browser checks canonical links, menu position, record reload, list history, switching, refusal, older links and staff bookmarks. Multiple independent examples do not prove a newly composed causal sequence without matching assertions.
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
- Customer root entry selects the remembered workspace.
- Record reload and list history retain their destinations.
- A direct settings address aligns menu and breadcrumb.
- An absent workspace identity yields not found.
- Switching rewrites a record destination to the new list.
- An older record link uses the selected customer workspace.
- An older bookmark reuses clearance retained through HQ landing.
- A cleared bookmark enters its workspace from both starts.
- Administrative navigation identifies the direct destination.
- Switching a record opens the corresponding new-workspace list.
- HQ landing keeps clearance useful for an older bookmark.
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 browser, console components, route builders, menu computation and client provider are real. Demonstration handlers and local fixture stores replace Platform responses; there is no real sign-in or service database in this tier.
Must Not Be Doubled
Do not replace the console’s routing, menu assembly, provider, destination guards or measured DOM with canned component outcomes. Demonstration responses or the declared controlled refusal are doubles at the response boundary, not substitutes for the console behavior under examination.