Platform snapshot pipeline

Verification Boundary

This suite exercises the local snapshot pipeline through its real worker and database. Cloud state-machine execution is represented by recorded starts and an in-process workflow walk.

What This Suite Proves

The local pipeline plans three workspaces, admits the eligible run, publishes a replacement, rejects corrupted self-test counts and purges owned fixtures. Its bound lifecycle scenario checks retained versions and the selected period after failed validation.

What It Does Not Prove

The small self-test does not establish cleanup of committed staging chunks for every snapshot generator or deployed Step Functions behavior. Registration supplies a verified assertion mapping, while the execution result remains unrecorded.

Real Dependencies and Test Doubles

PostgreSQL, the snapshot repository, planner, dispatcher, job engine, real run handler and self-test SQL execute locally. The file records Step Functions starts, walks the workflow in process and narrows the planner’s workspace loader to its fixtures. A temporary database trigger introduces invalid counts.

Must Not Be Doubled

Keep ledger writes, validation, publication transactions and purge statements real. Replacing these operations with fixture responses removes the publication and cleanup proof.