Batch integration deployed task handler

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

Submission, successful completion, ordinary recovery and replacement accounting use the actual task-handler entry with synthesized workflow steps. A refused database write must fail the job without a partial generation. 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

PostgreSQL, submission, synthesized workflow definitions and the actual task handler are exercised locally. Workflow start is captured by a double; preview invocation uses a client double that forwards the payload to the same handler.

Must Not Be Doubled

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