Keep staff work and workspace work in distinct contexts: 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.
HQ departure needs cache clearing before local removal, failed cleanup, retained context after a failed refresh and immediate re-entry races. Staff identity controls menu mode; the listed permission keys do not themselves prove every menu action is gated.
Interactions With Related Capabilities
HQ opens with a notice naming the refused workspace; neither an emergency-access dialog nor a workspace access banner appears.
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.