erio f7f2c82981 fix: use DB transaction return values for balance/quota notification crossing detection ...

Replace the stale Redis cache read + invalidation hack with direct DB
transaction RETURNING values:

- deductUsageBillingBalance: add RETURNING balance to get post-deduction balance
- incrementUsageBillingAccountQuota: extend RETURNING to include all 6 quota
  dimensions (daily/weekly/total used+limit)
- Expand UsageBillingApplyResult with NewBalance and QuotaState fields
- finalizePostUsageBilling uses result directly, no Redis read needed
- CheckAccountQuotaAfterIncrement accepts optional QuotaState to skip
  fetchFreshAccount when DB values are available

This eliminates the race condition where QueueDeductBalance async update
hadn't propagated to Redis before GetUserBalance read, causing oldBalance
to be inflated and threshold crossing detection to always fail.

2026-04-13 15:03:49 +08:00

..

jwtgen

fix claudecode review bug

2026-03-09 01:18:49 +08:00

server

fix: use DB transaction return values for balance/quota notification crossing detection

2026-04-13 15:03:49 +08:00