Enter the workspace named by a link: 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.
Entry needs every refusal, mismatched answers, encoded identifiers, unexpected failures, ten-second refusal-memory expiry and the six-second retry after leaving. Helper tests do not prove provider request reuse or mounting order.
Interactions With Related Capabilities
The pending destination shows no old contact body; successful entry clears SWR answers and mounts fresh workspace stores before the new list renders.
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.