Database checks for Threshold Notice

Verification Boundary

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

What This Suite Proves

Only active local administrators receive notices. Warning and pause messages use customer figures. Competing senders claim one delivery. Enclosing transactions defer notice delivery. Persistent delivery failure stops after three attempts. No-recipient warnings do not retry forever. Recovery retries committed owed notices. 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, crossing leases, production settlement, recipient resolution and real Administrator role assignments are real. The model, evidence bucket and email transport are scripted or recording doubles; no recipient inbox is contacted.

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.