---
id: TST-PFM-CSH-009
title: Development console addresses
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/dev/url-architecture.dev.spec.ts
implements:
  - ATS-PFM-CSH-009-05
  - ATS-PFM-CSH-010-02
  - ATS-PFM-CSH-013-02
environment: deployed-dev
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 15
isolation: >-
  Fresh browser context with existing development test accounts; licensing cases
  clean up only their own named overrides.
evidence:
  - >-
    react-console:e2e/dev/url-architecture.dev.spec.ts at
    baf6dae382d6f41dce976c7f848667ccc37e076f
  - >-
    react-console:e2e/dev/url-architecture.dev.spec.ts#a signed-out deep link
    goes through sign-in and comes back to the same page and query
  - >-
    react-console:e2e/dev/url-architecture.dev.spec.ts#an id no tenant has shows
    not found
  - >-
    react-console:e2e/dev/url-architecture.dev.spec.ts#signed out: sign-in comes
    back to that page and query in that tenant
  - >-
    react-console:e2e/dev/url-architecture.dev.spec.ts#signed in on Rhythm HQ:
    opening it goes straight into the tenant
binding_boundary:
  - scenario: ATS-PFM-CSH-009-05
    provenance: test
    source: >-
      react-console:e2e/dev/url-architecture.dev.spec.ts#a signed-out deep link
      goes through sign-in and comes back to the same page and query
    note: >-
      This file supplies the complete stated scenario outcome at its declared
      test boundary.
  - scenario: ATS-PFM-CSH-010-02
    provenance: test
    source: >-
      react-console:e2e/dev/url-architecture.dev.spec.ts#an id no tenant has
      shows not found
    note: >-
      This file supplies the listed assertions within a collective binding;
      another registered file supplies the other assertions.
  - scenario: ATS-PFM-CSH-013-02
    provenance: test
    source: >-
      react-console:e2e/dev/url-architecture.dev.spec.ts#signed out: sign-in
      comes back to that page and query in that tenant;
      react-console:e2e/dev/url-architecture.dev.spec.ts#signed in on Rhythm HQ:
      opening it goes straight into the tenant
    note: >-
      This file supplies the listed assertions within a collective binding;
      another registered file supplies the other assertions.
---

# Development console addresses

## Verification Boundary

Real sign-in and context reads check return to the same page and query, an unknown workspace and cleared staff bookmarks from signed-out and HQ starts. The nominal record-reload example actually opens a contacts list, so it supplies no record-identity binding.

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

- Sign-in returns to the requested page and query.
- An absent workspace identity yields not found.
- A cleared bookmark enters its workspace from both starts.

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, sign-in, development service responses and configured test accounts are real. The file uses its existing fixtures and secrets; no new response double is declared for the registered assertions.

## 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.