Custom record menu placement

Verification Boundary

Demonstration navigation checks grouped custom types, entries appended in a built-in section, inactive omissions and list-page filtering. The title mentions record pages but the second case actually opens the custom list; no record-detail binding is inferred.

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

• Placed types join built-in and custom-app navigation.
• A custom record keeps its menu entry reachable.

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.