Task refusal response codes

Verification Boundary

This suite checks deterministic module behavior with direct assertions.

The shared response mapper is checked for specific task conflict and eligibility codes, statuses, messages and error classes.

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)