Use a consistent console frame — acceptance

Coverage

The table separates scenarios with test bindings from proposed proof. A binding records a static examination of the test; it does not record a passing product test run.

Rule	Acceptance scenario
`BR-CAP-PFM-CSH-001-03`	`ATS-PFM-CSH-001-01` (bound)
`BR-CAP-PFM-CSH-001-04`	`ATS-PFM-CSH-001-02` (proposed), `ATS-PFM-CSH-001-03` (proposed)
`BR-CAP-PFM-CSH-001-05`	`ATS-PFM-CSH-001-04` (bound)
`BR-CAP-PFM-CSH-001-07`	`ATS-PFM-CSH-001-05` (proposed)

Test Scenarios

5 scenarios proving CAP-PFM-CSH-001; 2 bound to an existing test.

01 Access resolves before the working frame appearsbrowsertest

Proves: BR-CAP-PFM-CSH-001-03 AS-JNY-PFM-CSH-001-01
Preconditions: A signed-in console user starts with a fresh browser.
Steps: Observe the initial page and requests, then reload.
Expected: The security context is requested first; the working header, menu and page wait for its answer.
Data: A development account with console access.
Bound to: react-console:e2e/dev/initialisation.dev.spec.ts#asks the Platform exactly one thing first, and shows nothing until it is answered
react-console:e2e/dev/initialisation.dev.spec.ts#asks again on a reload, still before anything else
Source: react-console:e2e/dev/initialisation.dev.spec.ts#asks the Platform exactly one thing first, and shows nothing until it is answered

02 Retry recovers from an initial access-request failurebrowsernegativeproposed

Proves: BR-CAP-PFM-CSH-001-04
Preconditions: The first context request fails and the next can succeed.
Steps: Start the console and select Try Again.
Expected: The separate failure view offers retry and sign-out; a successful retry opens the console.
Data: A controlled failed response followed by a valid answer.
Source: react-console:components/console/console-boot-screens.tsx:consoleBootScreens

03 Refused access and missing setup have distinct explanationsunitnegativeproposed

Proves: BR-CAP-PFM-CSH-001-04
Preconditions: One session has no effective access; another build lacks required settings.
Steps: Render the two start-up conditions.
Expected: The access refusal identifies the account and offers sign-out; the setup view identifies missing settings.
Data: Refused access and incomplete configuration inputs.
Source: react-console:components/console/console-boot-screens.tsx:consoleBootScreens

04 A fallback workspace has a dismissible explanationbrowsertest

Proves: BR-CAP-PFM-CSH-001-05
Preconditions: The remembered workspace has become unavailable.
Steps: Open Rhythm, inspect the context notice and dismiss it.
Expected: The notice explains the changed starting context and disappears when dismissed while the console remains usable.
Data: A controlled refusal for the remembered workspace.
Bound to: react-console:e2e/controlled/tenant-unavailable.controlled.spec.ts#falls back to the default tenant, with a word of explanation, rather than refusing access
Source: react-console:e2e/controlled/tenant-unavailable.controlled.spec.ts#falls back to the default tenant, with a word of explanation, rather than refusing access

05 Sample amounts use the fixed conversion and rounding policyunitproposed

Proves: BR-CAP-PFM-CSH-001-07
Preconditions: Canadian dollars are selected for sample display.
Steps: Convert an amount from the base and back; format regular and compact values.
Expected: Conversion uses the fixed rate and cent rounding; display uses the specified ordinary and compact precision.
Data: Amounts on either side of a rounding boundary.
Source: react-console:components/console/console-provider.tsx:useMoney

Planning

Use a consistent console frame — acceptance ​

Coverage ​

Test Scenarios

Use a consistent console frame — acceptance

Coverage