Task persistence and lifecycle

Verification Boundary

This suite checks module reads, writes or presentation against persisted fixtures.

What This Suite Proves

Persistence assertions check task values, versioned edits, holder and queue stamps, claims, releases, closing and reopening, locks and foreign-workspace refusals.

The registered scenario bindings identify the assertion contributions this executable supplies. A compound scenario can require several suites.

What It Does Not Prove

It does not establish deployed Lambda transport, live Platform policy or end-user browser behavior.

Real Dependencies and Test Doubles

The actual persistence or presentation functions execute against the migrated PostgreSQL database and fixture execution contexts.

Must Not Be Doubled

The database queries, constraints, version checks, workspace policies and transaction boundaries under assertion remain real.