Strict workspace context reader

Verification Boundary

Doubled responses check the lowercased strict request, matching answers, classified refusals and rejection of a different workspace. Browser decoding, remembered refusal time and provider reuse are not asserted.

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

• A strict read refuses the wrong workspace answer.

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 context helper and its parsing and decision functions are real. Injected request functions answer independent in-memory fixtures, so transport and service authorization are doubled.

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.