Database checks for Run Operation

Verification Boundary

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

What This Suite Proves

Settlement distinguishes measured, unknown and absent usage. Exhausted turns return a bounded result. Bounded answers retain their charge. Refusal creates history without spending. Retries retain their own usage prices. Request and response capture have records. Redaction preserves ordinary text and replaces credentials. Exhausted allowance prevents another provider call. 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 catalog, ledger, request or task state writes, execution context and tool loop are real. The model is scripted and captured evidence uses memory storage; task telemetry is recorded where that suite asserts it.

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.