Object-scoped reach changes navigation and record actions together

Verification Boundary

This browser suite checks custom record journeys within the console’s mock target. The registered file and pinned revision define its boundary.

What This Suite Proves

The bindings identify the detailed or feature scenarios whose outcomes have assertions in this suite. Original case references remain attached to the detailed scenarios so a reviewer can inspect the exact assertion. Assertions are evidence of implemented checks; no execution result is claimed.

What It Does Not Prove

The register does not establish a current passing run or full specification conformance. Mock execution skips live-only branches; the mock result cannot qualify those outcomes. Browser assertions do not verify real server permission enforcement, database transactions or deployed delivery.

Real Dependencies and Test Doubles

The console components and browser actions run against mock service responses. Mock API handlers and browser-local persona permissions.

Must Not Be Doubled

A mock run must remain labeled as browser evidence. Real authorization, concurrency, commit-time history and storage cleanup require their own live or database-backed proof.