Task lifecycle decisions

Verification Boundary

This suite checks deterministic module behavior with direct assertions.

The decision table checks each unfinished-status move, dedicated closure and reopening, invalid closed-work moves and refusal codes.

The registered scenario bindings identify the assertion contributions this executable supplies. A compound scenario can require several suites.

It does not establish deployed Lambda transport, live Platform policy or end-user browser behavior.

The actual helper, schema, mapper or declaration under test runs with fixed inputs. These cases use no database or deployed service.

The decision, mapper, declaration or error response being asserted remains the real implementation.

Show evidence (sources, provenance, origins, pinned commits)