Schedules End To End integration suite

Verification Boundary

The suite exercises workspace operations against the migrated local database. Its fixtures and transaction contexts determine the records and service paths under test.

What This Suite Proves

The individual assertion references identify the acceptance outcomes this file exercises. When a scenario spans several suites, this file supplies only its listed assertions; qualification must include the other bindings and any recorded coverage finding.

What It Does Not Prove

Local database execution does not prove deployed infrastructure, external provider availability or console behavior. No result is claimed for the pinned revision until the suite runs and its evidence is reviewed.

Real Dependencies and Test Doubles

PostgreSQL, dispatcher, consumer, schedule repository and registered recurring work are real. A recording publisher stands for the queue, a manual clock fixes time, and the repeated-failure case doubles the period-lookup port.

Must Not Be Doubled

The database constraints, transaction paths and production persistence functions named by the assertions must remain real. A memory store cannot establish the recorded database proof.