Blocked ledger review and a fresh close

Verification Boundary

This browser suite exercises the live screens and public API observations recorded by its journey. It requires the coordinator’s isolated acceptance setup and serialized closing work.

What This Suite Proves

The journey reads both ledger blockers, observes execution revalidation refusal and attempts recovery before correcting and posting the source records. Its cancellation assertion conflicts with the service, so its later steps are not established as reachable.

What It Does Not Prove

The cancellation assertion expects a conflict where the service permits cancellation of the released failed run. Later correction steps are not established as reachable.

Real Dependencies and Test Doubles

The live console, Accounting APIs and authentication serve the run’s own business units and records. Fixture helpers also use CRM and the required payment infrastructure. This register does not claim those deployed dependencies were run.

Must Not Be Doubled

The public API authorization, close tasks, financial posting and retained records must remain real for the live acceptance outcomes.