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>
34 lines
1.0 KiB
TypeScript
34 lines
1.0 KiB
TypeScript
import type { SupabaseClient } from '@supabase/supabase-js'
|
|
import type { CapabilityKey } from './keys'
|
|
|
|
/**
|
|
* Append a usage event to metered_events. Best-effort and non-blocking:
|
|
* metering must never break the feature it measures, so failures are swallowed.
|
|
*
|
|
* Usage cannot be backfilled, so we capture it from day one even though no
|
|
* usage-based pricing exists yet: it is the raw material for future firm-level
|
|
* "active company" / consumption billing.
|
|
*/
|
|
export async function recordMeteredEvent(
|
|
supabase: SupabaseClient,
|
|
params: {
|
|
companyId: string
|
|
teamId?: string | null
|
|
key: CapabilityKey
|
|
eventType: string
|
|
attribution?: Record<string, unknown>
|
|
},
|
|
): Promise<void> {
|
|
try {
|
|
await supabase.from('metered_events').insert({
|
|
company_id: params.companyId,
|
|
team_id: params.teamId ?? null,
|
|
capability_key: params.key,
|
|
event_type: params.eventType,
|
|
attribution: params.attribution ?? {},
|
|
})
|
|
} catch {
|
|
// best-effort; never block the metered operation
|
|
}
|
|
}
|