fix(billing): bound cumulative usage lock holders

[icecrasher321]

Summary

• Bound cumulative billing transactions on the server so a stalled holder releases its per-event lock and existing same-key retries can recover. Preserve cumulative maximum, exact billed delta, attribution checks, and settlement replay.
• Record slow or failed transaction stage timings to distinguish pool, lock, query, and commit delays.
• Patch the pinned PostgreSQL driver with the transaction closure guard from upstream PR #1155, preventing resumed transaction handles from crashing or writing through a replacement session.

Type of Change

• Bug fix

Testing

101 targeted tests pass on PostgreSQL 17, plus the eight recovery regressions on PostgreSQL 16. These cover idle-holder reproduction, INSERT/UPDATE rollback, exact retry accounting, concurrent cumulative callbacks, attribution checks, and ESM/CommonJS reconnection. Workspace lint/type-check, all 46 audits, and fresh patch installation with the repository-pinned Bun version pass.

PostgreSQL 17+ uses a four-second total transaction budget. Older supported servers use a four-second idle-transaction budget alongside bounded statement and lock waits. These budgets do not cover pool acquisition, billing-context resolution, or settlement.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Sep 9, 2026 5:47pm UTC

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge; no outstanding correctness, security, or repository-rule issue remains.

Summary

• Uses PostgreSQL 17+ transaction deadlines with a PostgreSQL 15/16 idle-transaction fallback.
• Adds stage-level timing diagnostics for slow or failed billing transactions.
• Patches the pinned PostgreSQL driver to reject resumed transaction queries after connection closure.
• Adds PostgreSQL 16/17 recovery coverage for rollback, reconnection, concurrency, attribution, and exact cumulative accounting.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Resolve billing context] --> B[Acquire pooled transaction]
    B --> C[Configure transaction, statement, and lock timeouts]
    C --> D[Acquire event-key advisory lock]
    D --> E[Read existing cumulative usage]
    E --> F{Incoming total is higher?}
    F -- No --> G[Commit without billing]
    F -- Yes --> H[Insert or update exact cumulative total]
    H --> I[Commit billed delta]
    C -. stalled transaction .-> J[PostgreSQL closes session and rolls back]
    D -. bounded lock wait .-> K[Retryable lock timeout]
    J --> L[Patched driver rejects resumed transaction handle]
    K --> M[Same-key retry]
    L --> M
    M --> B

Loading

[icecrasher321]

@greptile

[icecrasher321]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@icecrasher321 I have started the AI code review. It will take a few minutes to complete.

[icecrasher321]

@greptile