Unavailable remembered workspace

Verification Boundary

A real sign-in establishes workspace memory; intercepted named-context reads then report unavailability. The default-context read continues to the service, and the browser checks working fallback and notice dismissal.

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

• Fallback notice can be dismissed without losing work.

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, sign-in session and unmodified development reads are real. The named context response is fulfilled by the test with a deterministic refusal; that interception is part of this controlled boundary.

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.