Jakob WennbergandClaude Sonnet 5
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>
48 lines
1.7 KiB
TypeScript
48 lines
1.7 KiB
TypeScript
import type { AgentIntent } from './types'
|
|
import { generalHelp } from './general-help'
|
|
import { transactionCategorization } from './transaction-categorization'
|
|
import { inboxBulkBook } from './inbox-bulk-book'
|
|
import { invoiceDraft } from './invoice-draft'
|
|
import { supplierInvoiceReview } from './supplier-invoice-review'
|
|
import { vatReview } from './vat-review'
|
|
import { bokslutStep } from './bokslut-step'
|
|
import { verifikationDraft } from './verifikation-draft'
|
|
import { kpiExplain } from './kpi-explain'
|
|
import { settingsHelp } from './settings-help'
|
|
import { onboardingEmpty } from './onboarding-empty'
|
|
import { onboardingIntake } from './onboarding-intake'
|
|
|
|
// Static intent table. Adding a new intent: write a file under
|
|
// lib/agent/intents/<id>.ts that calls defineAgentIntent({...}), import it
|
|
// here, append it to INTENTS, and it's reachable from /api/agent/invoke.
|
|
// Plan refs: §8 (intent system).
|
|
//
|
|
// Using a static table (not a registry singleton) on purpose: intents are
|
|
// pure code, not data. Their lifetime matches the deployment.
|
|
|
|
// eslint-disable-next-line @typescript-eslint/no-explicit-any
|
|
const INTENTS: AgentIntent<any, any>[] = [
|
|
generalHelp,
|
|
transactionCategorization,
|
|
inboxBulkBook,
|
|
invoiceDraft,
|
|
supplierInvoiceReview,
|
|
vatReview,
|
|
bokslutStep,
|
|
verifikationDraft,
|
|
kpiExplain,
|
|
settingsHelp,
|
|
onboardingEmpty,
|
|
onboardingIntake,
|
|
]
|
|
|
|
// eslint-disable-next-line @typescript-eslint/no-explicit-any
|
|
export function getIntent(id: string): AgentIntent<any, any> | undefined {
|
|
return INTENTS.find((i) => i.id === id)
|
|
}
|
|
|
|
// eslint-disable-next-line @typescript-eslint/no-explicit-any
|
|
export function listIntents(): AgentIntent<any, any>[] {
|
|
return INTENTS
|
|
}
|