Job root status model

Verification Boundary

This suite exercises background work through its declared function or structural boundary. Its implementation is present at the pinned source revision, and this register records no execution result.

What This Suite Proves

The checks enumerate root commands against every starting status and inspect accepted outcomes, settlement time, progress and unchanged final records. The scenario bindings name the attributed outcomes.

What It Does Not Prove

Local execution does not establish deployed infrastructure, live commercial-provider configuration or authorization-cache completion. Registration and an implemented suite do not establish a passing result.

Real Dependencies and Test Doubles

The production logic under assertion is real. Storage uses the suite’s in-memory records rather than a durable database. Execution clients or probes use the suite’s controlled response port. Boundary cases control the clock.

Must Not Be Doubled

The production function, registry or builder under assertion remains real.