Explain why an application page cannot open: Capability Test Specification
Coverage
The coverage map describes specified proof, not a passing run. Each mandatory rule below has a scenario or an explicit finding; a proposed scenario remains an execution obligation even when its expected outcome follows the pinned implementation.
Destination coverage needs application precedence, readable personal refusal, explicit and alternative domains, requested-workspace gating and return controls. Unconditional overview links must be distinguished from the overview’s independent guard.
Interactions With Related Capabilities
The unavailable body offers a route to the Applications overview; the overview applies its own page guard.
The interaction rows cite the contracts they exercise. Related combinations without a complete case remain in the coverage finding, together with cross-capability workflows and permission boundaries. A helper assertion is bound only for its stated outcome; the full browser handoff remains proposed until a suite checks it.
Pinned source and exact test anchors are recorded in frontmatter. Test bindings record static assertion review and use the executable-suite register; no product test result is inferred from that review. The prior planning and design examinations supply context, while this continuation records the remaining proof obligations explicitly.