Batch integration concurrent posting

Verification Boundary

This suite exercises the imported batch services or storage against the prepared local database. It does not imply that a deployed workflow is contacted.

What This Suite Proves

A direct posting or recovery waits for a competing row lock and checks the committed state before proceeding. The assertion anchors identify the supported portions of the bound scenarios.

What It Does Not Prove

Local assertions do not establish deployment configuration, remote delivery guarantees, or unasserted lifecycle and concurrency paths.

Real Dependencies and Test Doubles

The application database connection runs the real direct engine. A separate owner connection holds a controlled status mutation open to establish blocking; it does not run a second full posting engine.

Must Not Be Doubled

The database constraints, transaction boundaries and exercised accounting functions must remain real when qualifying the asserted persistence or generation behavior.