Duplicate console with mock responses
Verification Boundary
A real browser and production console components consume MSW responses. CRM transactions, background jobs and permission evaluation are replaced by handlers.
What This Suite Proves
The queue, record entry points and merge workspace use the console adapters, display refusals and expose actions according to supplied permission keys. No capability scenario is mapped to this selection yet; its file inventory records existing executable coverage without assigning product proof. No control claim is assigned without a check that fails when the control is removed.
What It Does Not Prove
Mock responses do not prove service authorization, persistence or atomicity. The service integration and local API registers carry those boundaries.
Level and Rationale
A browser is needed to check the visible controls, navigation and adapter requests. Lower-level service checks cannot establish those screen outcomes.
Lifecycle Coverage
Plan creation, review changes and merge completion receive partial credit only for their browser behavior against mock responses. They establish no CRM persistence or transaction result. Deletion is not exercised: closing a browser context is fixture cleanup, not a record lifecycle assertion. Archive and reconciliation remain outside this selection.
Real Dependencies and Test Doubles
A real browser and production console components consume MSW responses. CRM transactions, background jobs and permission evaluation are replaced by handlers.
Must Not Be Doubled
Keep the rendered components and request adapters real; replacing them would remove the console behavior under examination.
Fixtures and Isolation
The mock project supplies fixed records and response handlers in each browser context. These selections do not change deployed rules or need shared-service cleanup.
Determinism and Retries
The register records no new runtime result. Existing polling and fixture clocks remain part of the authored tests; polling for completion is not a retry of a failed case. Run with at most three workers and diagnose a failure before rerunning it.
How It Runs
The frontmatter records the scoped command and its runner tier. Supply the configuration and fixtures required by that Playwright project.
Coverage Gaps
The selection has no scenario mapping; mapping requires comparing the assertions with a complete scenario outcome. The capability gap records identify unbound obligations, and the grouped-suite finding records incomplete lifecycle and runtime coverage.