Close, reopen and retained-record API lifecycle

Verification Boundary

The suite exercises the local public API dispatcher with signed request contexts and PostgreSQL. Durable work uses the in-process runner. AWS workflow delivery and a deployed console are outside this verification boundary.

What This Suite Proves

The local API suite submits a close, follows its six steps, reads its retained record and reopens it. It checks replay, validation, missing grants, foreign runs and recovery refusals on ineligible outcomes.

What It Does Not Prove

This register records assertion scope without claiming a passing run or complete coverage of every rule and scenario variant.

Real Dependencies and Test Doubles

The local dispatcher, access and permission enforcement, domain services and database are exercised. Signing keys and workspace registration use local fixtures, and durable jobs use the in-process runner. This is a local API test, not a deployed authentication or workflow test.

Must Not Be Doubled

Keep the dispatcher’s enforced grants, request validation, production persistence and database constraints real. A local runner cannot substitute for deployed workflow qualification.