8 Commits

Include renames

Author	SHA1	Message	Date
Daniel Salazar	cf9df8719a	fix(alarm): forget idle alarms and cap how many the client holds (#4171) ... AlarmClient kept every alarm id it had seen for the life of the process, and ids that embed a user, key or invoice grew it without bound. The registry is now ordered by last occurrence: alarms idle for 24 hours are dropped on the next create, and past 1000 the least recently raised goes first. Clearing or evicting an alarm only removes its short-id alias when the alias still points at it.	2026-10-11 17:54:26 -07:00
Daniel Salazar	6060de8fbd	fix(alerts): overspend alarm in credits at warning; no-choices completions stop paging (#4154) ... - The per-account overspend alarm now reads in credits and raises at warning so it reaches the pager instead of only chat. - A non-stream completion with no choices (an upstream answering 200 with an error body) threw a TypeError that classified as internal_error and paged critical. It now throws bad_response, which falls back like any other empty response and surfaces as a 400.	2026-10-09 18:13:44 -07:00
404oopsandClaude Fable 5.1	c8f4906af4	fix(ai): keep per-provider failures when every chat route fails (#3836) ... When the chat fallback chain is exhausted, the driver already records each attempt (model, provider, status, code, message, timeout) in the error's `fields.attempts`, but the alarm keyed on the classified message alone and the alarm client printed the error at inspect depth 2, so the log and Slack line read `internal_error:All providers failed` with nothing about which providers failed or why. Deduped repeats printed only a count. - The HTTP alarm gate now attaches an HttpError's `fields` to the alarm under a single `details` key. One key can't shadow the gate's own request fields, and a repeat from another thrower on a shared id replaces it instead of merging into it. - The chat driver logs one warn line per exhausted chain with the completion id, the resolved route, the classified code and the attempts as JSON, so every occurrence is greppable by trace even when the alarm dedupes it. Chains marked `noAlarm` don't log. - Docs: `fields` reaches both the client and the alarm, so it has to be safe to show the caller. Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>	2026-09-09 14:56:11 -07:00
Daniel Salazar	afe46a17a0	fix: alaem cascade (#3668)	2026-08-29 03:41:23 -07:00
Daniel Salazar	fb7968a1c7	fix: metering hardening; handle burst of unfinished ai requests (#3585)	2026-08-15 10:52:29 -07:00
Daniel Salazar	79d4201f12	fix: rate limits, AI routing, and a type-check gate (#3529) ... - declare rate + concurrency limits on every route and driver that lacked one - add acquireConcurrent for websocket connections and the DAV mount - bucket AI models by identity key only; keep resold duplicates of any vendor - skip recently-failed provider routes; cap the fallback chain at 3 attempts - let full-access access tokens bind a worker to an app their own user owns - cache resolved subscriptions so tiered limits don't add a round trip	2026-08-10 19:09:47 -07:00
Daniel Salazar	84582ee33d	fix: alarm channels (#3491)	2026-08-01 15:55:06 -07:00
Daniel Salazar	7d0d44aef9	feat: slack alarms (#3489)	2026-08-01 13:12:41 -07:00