ZyyandClaude Fable 5 d199141a91 feat(store): materialize quota_limit_reached for single-source limit status ...

Dashboard reads the materialized column instead of parsing raw quota
JSON (design §3.3/§5.3): Provider computes snapshot-level limit_reached
on quota writes, store persists it, Admin account_status and Dashboard
both consume the same value.

- QuotaObservation gains limit_reached; openai writes fact.exhausted()
  (429 always true), xai writes used_percent>=100
- compare_and_swap_provider_quota updates the column; get_quotas and
  ACCOUNT_SELECT read it back
- ProviderAccountSummary carries quota_limit_reached; admin_account_status
  derives RateLimited from it (Unknown -> Invalid)
- Dashboard provider_account_metrics reads quota_limit_reached instead of
  provider_quota_json->'rate_limit'
- Migration 0003 adds the column with backfill (coalesce for NULL when
  rate_limit key is absent); 0004 fixes NULL backfill for already-applied
  environments

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-08-03 03:32:17 +08:00

..

apps/gateway

test(gateway): sync config rejection fixtures to current example

2026-08-02 02:20:29 +08:00

crates

feat(store): materialize quota_limit_reached for single-source limit status

2026-08-03 03:32:17 +08:00

migrations

feat(store): materialize quota_limit_reached for single-source limit status

2026-08-03 03:32:17 +08:00

Cargo.lock

feat(openai): zstd-compress responses request bodies like the official client

2026-08-02 02:27:46 +08:00

Cargo.toml

refactor(backend): finalize gateway package boundaries

2026-07-25 00:33:11 +08:00

rust-toolchain.toml

refactor: migrate backend to Rust 1.97 and edition 2024

2026-07-12 19:10:56 +08:00