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>
41 lines
1.6 KiB
TypeScript
41 lines
1.6 KiB
TypeScript
/**
|
|
* Transaction-scoped actor context for journal-entry commits: isomorphic half.
|
|
*
|
|
* Carries WHO is relaying a commit (api_key | user | agent_chat | …) from the
|
|
* approval entry points down to commitEntry() without threading a parameter
|
|
* through every pending-operation executor and entry-generator in between.
|
|
* commitEntry() reads it as a fallback and forwards it to the
|
|
* commit_journal_entry RPC, which stamps journal_entries.committed_actor_* and
|
|
* the audit_log COMMIT row (migration 20260619120000).
|
|
*
|
|
* engine.ts is reachable from client component bundles (e.g. the invoice
|
|
* detail page), and client chunks cannot load node:async_hooks: so this
|
|
* module holds only the type + a storage registry, and the AsyncLocalStorage
|
|
* implementation lives in ./actor-context-node (server-only, imported by the
|
|
* approval paths). In a client bundle the registry stays empty and getActor()
|
|
* returns undefined: the same no-attribution default as a server call
|
|
* outside a runWithActor() scope.
|
|
*/
|
|
export interface CommitActor {
|
|
/** Matches the journal_entries.committed_actor_type CHECK constraint. */
|
|
type: 'user' | 'api_key' | 'mcp_oauth' | 'cron' | 'system' | 'agent_chat'
|
|
/** Human-readable credential label, e.g. the API key name. */
|
|
label?: string
|
|
}
|
|
|
|
export interface ActorStore {
|
|
getStore(): CommitActor | undefined
|
|
}
|
|
|
|
let store: ActorStore | null = null
|
|
|
|
/** Bind the server-side AsyncLocalStorage. Called by ./actor-context-node. */
|
|
export function bindActorStore(s: ActorStore): void {
|
|
store = s
|
|
}
|
|
|
|
/** The actor for the current async execution scope, if any. */
|
|
export function getActor(): CommitActor | undefined {
|
|
return store?.getStore()
|
|
}
|