Recurring report delivery 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 and service readbacks check a successful timed delivery, a report-access withdrawal, a failed occurrence with no export or messages, refused owner takeover and administrator recovery. Later timed delivery verifies the resumed schedule under its new owner.

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 APIs, acceptance personas, published communication template and recipient mailbox service supply the journey. Hourly occurrences use the development clock; the file permits a 160-minute run.

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.