---
id: TST-PFM-CSH-013
title: Staff HQ landing
kind: browser-lifecycle
product_area: platform
module: console-shell
revision: 1
status: draft
source_sha:
  rhythm-v2-docs: 25e253cb434aac6603ee294e3ca197ab6c4bfd0b
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: react-console
files:
  - e2e/mock/staff-landing.mock.spec.ts
implements:
  - ATS-PFM-CSH-013-01
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: Fresh browser context and demonstration local stores per test.
evidence:
  - >-
    react-console:e2e/mock/staff-landing.mock.spec.ts at
    baf6dae382d6f41dce976c7f848667ccc37e076f
  - >-
    react-console:e2e/mock/staff-landing.mock.spec.ts#a staff member with a
    remembered tenant and a standing grant lands on /hq in HQ context
binding_boundary:
  - scenario: ATS-PFM-CSH-013-01
    provenance: test
    source: >-
      react-console:e2e/mock/staff-landing.mock.spec.ts#a staff member with a
      remembered tenant and a standing grant lands on /hq in HQ context
    note: >-
      This file supplies the complete stated scenario outcome at its declared
      test boundary.
---

# Staff HQ landing

## Verification Boundary

The browser establishes staff workspace memory and reloads the bare root. It asserts HQ links, absent customer navigation and selector, no staff-access banner and preserved workspace memory.

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

- Staff root landing retains memory without selecting it.

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.