Report catalog and source sharing browser journey

Verification Boundary

This suite drives the configured console and checks development-service readbacks. The registered assertions describe the source at the pinned revision; no application run is recorded by this examination.

What This Suite Proves

The browser saves a customized report copy, observes a source-audience sharing conflict, shares the source and report, then compares a colleague’s displayed totals with independently read ledger totals. It also checks read-only access and refusal of an API edit.

What It Does Not Prove

The journey does not establish every permission combination, source invariant or delivery failure mode. Registration supplies a verified assertion mapping, while the execution result remains unrecorded.

Real Dependencies and Test Doubles

The configured console, Platform and Accounting APIs, retained acceptance personas and run-owned ledger records supply the journey. Setup and cleanup helpers create and remove the journey’s records.

Must Not Be Doubled

Keep the browser actions, service access checks and readbacks used by the bound scenario real. Injecting successful responses would remove the claimed sharing or recovery proof.