Obligations queries

Verification Boundary

This suite checks obligations queries against the prepared PostgreSQL database. Its entry points are the persistence and service functions used by the tests.

What This Suite Proves

The suite’s source cases exercise the registered boundary, but this back-fill does not map them to a complete capability or feature scenario. The executable record remains useful without an invented scenario binding.

What It Does Not Prove

Direct service and persistence calls do not establish the full HTTP permission contract, deployed scheduling or browser behavior. No execution result is claimed by this register.

Real Dependencies and Test Doubles

The database and imported Commerce persistence services are real. Fixtures create the records owned by this run. Time-sensitive cases use a controlled clock where the source fixture supplies one.

Must Not Be Doubled

Keep the database constraints, row visibility and persistence writes real when claiming this integration coverage. A canned repository response cannot replace the boundary being checked.