Entities database and persistence integration
Verification Boundary
Direct-table tests and service tests exercise contact and organization aggregates, affiliation periods, detail-source disconnection, locks, revisions, effective definitions, compliance reprocessing and template compensation against PostgreSQL. This register groups 98 files with a common verification boundary; it does not register each file as an independent suite. Files and assertion sources remain explicit so an operator can select the group without losing the narrower proof boundaries.
What This Suite Proves
Direct-table tests and service tests exercise contact and organization aggregates, affiliation periods, detail-source disconnection, locks, revisions, effective definitions, compliance reprocessing and template compensation against PostgreSQL. The structured bindings retain the previously recorded contributions. An unbound file supplies no newly asserted specification coverage. No execution result is claimed by this registration.
What It Does Not Prove
Direct service calls bypass the HTTP authorizer. Storage, template and other remote doubles only establish the asserted interaction and failure handling, not deployed service settlement. A bound contribution is evidence for its assertions rather than certification of an entire composite scenario. Skipped or environment-dependent declarations remain visible in the source observations.
Real Dependencies and Test Doubles
Prepare the test database before execution. Real constraints, workspace policies, transaction behavior and persistence functions are required. Individual tests declare remote storage, template or execution-context doubles. The evidence list and per-file source observations identify the existing tests and their declared dependencies.
Must Not Be Doubled
Keep PostgreSQL and the persistence behavior under test. For local API checks, also keep the dispatcher, route declarations and permission evaluation real.