Jakob Wennberg
ec27228a8e
Em dashes (—) and en dashes (–) had spread across comments, docs, tests, and a few UI strings, reading as AI-generated boilerplate rather than house style. Replaced each with punctuation matching its context: colon for explanatory clauses, comma for asides, plain hyphen for numeric/legal ranges (e.g. "21-23§"), "to"/"till" for date ranges, parentheses for paired-dash asides. messages/en.json and messages/sv.json were fixed by hand together to keep sv/en in sync. Left untouched where the dash is the functional subject rather than decorative punctuation: date-range-parser.ts's separator regex, charset-repair.ts's CP1252 byte-mapping table (and its test), the SIE encoding mojibake docs, generic-csv.ts's minus-sign normalizer, the agent system-prompt files that already instruct against em dashes, and a golden iXBRL test fixture compared byte-for-byte. Also fixes two bugs surfaced along the way: an off-by-one in ApiKeysPanel's scope-label split (a leftover from an earlier partial pass), and a charset-repair test that had lost the literal en-dash it exists to verify. Regenerated the agent atom seed migration (skills:generate) since 27 SKILL.md files changed. Added a CLAUDE.md rule against em/en dashes, with an explicit carve-out for the functional-dash cases above. Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
57 lines
1.9 KiB
TypeScript
57 lines
1.9 KiB
TypeScript
import type { SupabaseClient } from '@supabase/supabase-js'
|
|
|
|
/**
|
|
* Per-user rate limiter for the in-app AI agent's LLM endpoints
|
|
* (/api/agent/invoke, /onboarding/stream, /composer). Backed by the
|
|
* `check_and_increment_agent_quota` Postgres RPC (atomic check + increment):
|
|
* same shared store the rest of the app uses, no Upstash/env dependency.
|
|
*
|
|
* Limits are deliberately GENEROUS: a normal heavy user (dozens of turns a day)
|
|
* never hits them. The cap exists only to bound runaway Bedrock spend from a
|
|
* loop-firing session or reload-spammed onboarding. Keyed per-user.
|
|
*/
|
|
export interface AgentLimitResult {
|
|
ok: boolean
|
|
retryAfterSec?: number
|
|
scope?: 'minute' | 'day'
|
|
}
|
|
|
|
const MINUTE_MAX = 30
|
|
const DAY_MAX = 1000
|
|
|
|
export async function checkAgentRateLimit(
|
|
supabase: SupabaseClient,
|
|
userId: string,
|
|
): Promise<AgentLimitResult> {
|
|
const { data, error } = await supabase.rpc('check_and_increment_agent_quota', {
|
|
p_user_id: userId,
|
|
p_minute_max: MINUTE_MAX,
|
|
p_day_max: DAY_MAX,
|
|
})
|
|
if (error) {
|
|
// Fail open on infra error: the limiter is defense-in-depth; better to
|
|
// serve a real user than to 429 them because the RPC blipped.
|
|
console.error('[agent-rate-limit] RPC failed:', error)
|
|
return { ok: true }
|
|
}
|
|
const result = (data ?? { ok: true }) as {
|
|
ok: boolean
|
|
scope?: 'minute' | 'day'
|
|
retry_after_sec?: number
|
|
}
|
|
return { ok: result.ok, scope: result.scope, retryAfterSec: result.retry_after_sec }
|
|
}
|
|
|
|
/**
|
|
* Standard 429 JSON body for a rate-limited agent request. The chat client
|
|
* surfaces `error` verbatim, so keep it a friendly Swedish sentence.
|
|
*/
|
|
export function agentRateLimitResponseBody(result: AgentLimitResult): { error: string } {
|
|
return {
|
|
error:
|
|
result.scope === 'day'
|
|
? 'Du har nått dagens gräns för förfrågningar till assistenten. Försök igen senare.'
|
|
: 'För många förfrågningar till assistenten just nu. Vänta en stund och försök igen.',
|
|
}
|
|
}
|