Read-only readiness and evaluator savepoints

Verification Boundary

This suite exercises the named persistence or service behavior on the local integration database. Its bindings can cover parts of a combined capability scenario.

What This Suite Proves

The transaction suite checks standalone read-only behavior, refusal of a write, joining a writable caller transaction and rolling a failed evaluator back before another database query succeeds.

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 suite uses local PostgreSQL with the application persistence and its declared constraints. Fixture contexts supply callers and time. Durable job suites run the task handlers in process and selected fault cases replace financial ports.

Must Not Be Doubled

The persistence and database constraints under assertion must remain real. A financial port stand-in cannot qualify actual recognition or reversal; those outcomes require the real posting suite.