Database checks for Materialize Catalog

Verification Boundary

The suite checks module persistence or service behavior against prepared PostgreSQL with scoped records.

What This Suite Proves

Invalid catalog publication is atomic. Unchanged publication leaves history alone. Combined bindings require every named suite; a component assertion alone does not establish the full experiment.

What It Does Not Prove

The suite does not establish browser behavior, deployed routing, live model quality or actual recipient inbox delivery.

Real Dependencies and Test Doubles

PostgreSQL, the validator, publication logic and both history persistence services are real. Invalid catalog declarations are literal fixtures.

Must Not Be Doubled

Retain PostgreSQL constraints, transaction behavior and the production persistence or dispatcher path under test. A scripted provider must not replace accounting or authorization.