[WRONG BRANCH] fix(quota): hydrate and persist account quota snapshots

[luvs01]

Motivation

• The runtime declared disk-backed helpers for per-account quota snapshots but never wired them into production reads or successful probe updates, so evidence was lost across restarts and pre-dispatch ranking remained blind.
• Persisting newly measured Anthropic/Kiro per-account quota to disk ensures restart-time ordering uses last-known headroom and avoids wasted rotation retries.
• Add a small integration regression to prove disk→runtime hydration and that ordinary probes schedule a debounced snapshot write.

Description

• Seed the in-memory per-account quota map from the persisted snapshot by calling hydrateAccountQuotaCache() from routing-facing reads and reconciliation points.
• Schedule debounced disk writes by calling persistAccountQuotaCache() after successful Anthropic and Kiro provider-level probes and after successful per-account probes.
• Add a test-only reset helper resetProviderAccountQuotaDiskStateForTests() and update persistence tests to assert that persisted rows hydrate the runtime cache and that production probes schedule writes.
• Make clearAccountQuotaCache() avoid re-seeding from the file just cleared to prevent races with immediate file-backed writes.

Testing

• ✅ Ran focused tests: node_modules/bun/bin/bun.exe test tests/provider-account-quota-persistence.test.ts tests/provider-account-quota.test.ts and observed the added persistence/hydration assertions pass (23 tests).
• ✅ Typecheck succeeded with node_modules/bun/bin/bun.exe run typecheck.
• ✅ Privacy scan succeeded with node_modules/bun/bin/bun.exe run privacy:scan.
• ❌ Full suite attempted (node_modules/bun/bin/bun.exe run test) but encountered unrelated, pre-existing failures in other subsystems (lab automation and a few integration tests); these unrelated failures prevented a completed full-suite run in this environment.

---

Codex Task

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: b1a6243a-b4ec-4345-aa0c-2e29a412428c

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-08-31T01:07:00.245163Z	6087fbe	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[github-actions]

✅ Deterministic PR hygiene checks passed.

[github-actions]

⏳ DRAFT

• wrong target branch (main); retarget to dev.

What to do

• Retarget this PR to dev — all contributions go to dev.

Its title has been prefixed with [WRONG BRANCH].
This pull request was already a draft. Its draft status will be preserved after every issue above is resolved.