Database checks for AI Settlement Sweep
Verification Boundary
The suite checks module persistence or service behavior against prepared PostgreSQL with scoped records.
What This Suite Proves
Recovery releases an eligible recorded hold. Old nonterminal requests receive estimated settlement. Recent work remains untouched. Successful recovery is not charged twice. 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, production sweep, per-workspace pass, ledger and request-state comparisons are real. A fixed clock controls eligibility; settlement statements are not doubled.
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.