Files
accounted/extensions/general/mcp-server/resources/capabilities.ts
T
Jakob Wennberg ec27228a8e style: remove em/en dashes repo-wide, add CLAUDE.md rule against them (#890)
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>
2026-07-04 15:58:06 +02:00

85 lines
3.0 KiB
TypeScript

import type { McpResource } from './types'
import { TOOL_SCOPE_MAP, hasScope } from '@/lib/auth/api-keys'
interface Capability {
tool: string
scope: string
granted: boolean
state_blocked: boolean
reason: string | null
}
export const capabilitiesResource: McpResource = {
uri: 'Accounted://capabilities',
name: 'Capabilities',
description: 'What the current API key can actually do given (a) its granted scopes and (b) the current company state. Surfaces blockers like locked periods so the agent knows ahead of time why an action would fail.',
mimeType: 'application/json',
read: async ({ supabase, companyId, scopes }) => {
const today = new Date().toISOString().slice(0, 10)
const { data: activePeriod } = await supabase
.from('fiscal_periods')
.select('id, is_closed, locked_at, opening_balances_set, period_end')
.eq('company_id', companyId)
.lte('period_start', today)
.gte('period_end', today)
.maybeSingle()
const { data: settings } = await supabase
.from('company_settings')
.select('bookkeeping_locked_through, vat_registered, pays_salaries')
.eq('company_id', companyId)
.maybeSingle()
const periodIsLocked = !!activePeriod?.locked_at || !!activePeriod?.is_closed
const periodMissing = !activePeriod
const companyLocked = !!settings?.bookkeeping_locked_through
&& settings.bookkeeping_locked_through >= today
const stateBlockers: Record<string, string | null> = {
// Scope → reason it's blocked by current state, or null
'transactions:write': periodMissing
? 'No fiscal period covers today\'s date: open a period first'
: periodIsLocked
? 'Active period is closed/locked'
: companyLocked
? 'Company-wide bookkeeping lock is in effect'
: null,
'invoices:write': periodMissing ? 'No fiscal period covers today\'s date' : null,
'payroll:write': !settings?.pays_salaries
? 'Company is not configured to pay salaries (settings.pays_salaries=false)'
: null,
}
const capabilities: Capability[] = Object.entries(TOOL_SCOPE_MAP).map(
([tool, scope]) => {
const granted = hasScope(scopes, scope)
const stateReason = stateBlockers[scope] ?? null
return {
tool,
scope,
granted,
state_blocked: granted && !!stateReason,
reason: !granted
? `Scope "${scope}" not granted to this API key`
: stateReason,
}
}
)
return {
granted_scopes: scopes,
active_period: activePeriod ?? null,
company_lock_date: settings?.bookkeeping_locked_through ?? null,
vat_registered: settings?.vat_registered ?? false,
pays_salaries: settings?.pays_salaries ?? false,
capabilities,
summary: {
total: capabilities.length,
granted: capabilities.filter((c) => c.granted).length,
state_blocked: capabilities.filter((c) => c.state_blocked).length,
},
}
},
}