Report views execution
Read the exact action guide for prerequisites, identifier discovery, supported input, effects, captured successful and refused responses, verification and recovery. Synthetic fixture results do not authorize a live mutation or establish a provider outcome.
- List saved report views: List the named filter sets saved for one report in this workspace, including the exact URL parameters each view restores.
- Create saved report view: Save one report filter set under a workspace-wide name. Names are unique within that report and the report key cannot change later.
- Update saved report view: Rename a saved report view or replace its stored filter parameters. The report it belongs to does not change.
- Delete saved report view: Permanently remove one saved report filter set from this workspace. The report and its accounting data are unchanged.
Evidence
Actual Books route handlers and the exported Worker were exercised against five local SQLite D1 concern databases with all committed migrations, the real posting Durable Object and local R2. Route captures use synthetic verified Auth; Worker captures use synthetic Auth transports. Nexus, Brand, Notify, Pay, Mercury and Xero responses are explicitly simulated at the provider transport boundary. Captures prove local request/response behavior and canonical SDK projection, not live bank access, payment movement, email delivery, provider eligibility, tax compliance, encrypted custody, scheduled execution, deployment or production completion. Fixture identities, credentials, addresses and records authorize no live operation.