Customer application overview on development

Verification Boundary

The registered shell assertions inspect the customer administrator’s overview and readable state labels. The file also changes and cleans up its own HQ licensing overrides, which Operations owns; the register does not assign those writes to the shell.

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

• The development overview displays customer-facing state labels.

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, development service responses and configured test accounts are real. The file uses its existing fixtures and secrets; no new response double is declared for the registered assertions.

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.