Application access in the browser

Verification Boundary

Demonstration sessions check omitted application sections, blocked and usable destinations, overview wording and application-coded refusal refresh. Policy editing and HQ override operations elsewhere in this file are outside the shell’s ownership.

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

• An omitted product contributes no sidebar section.
• A coded refusal refreshes offered applications.
• A coded refusal changes the menu in the same session.
• The overview explains its demonstration fixture rows.
• A coded refusal corrects the existing launcher.

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.