* feat(reconciliation): skattekonto bridge engine, sync-time twin proposals, account-keyed facade The engine half of the reconciliation page (design: Avstämningsmotorn). - lib/reconciliation/skattekonto-reconciliation.ts: getSkattekontoReconciliationStatus anchors at the saldo snapshot and returns the bridge (saldo hos Skatteverket, händelser som saknas, 1630-rader utan händelse, ignorerade, ingående skillnad, bokfört), the item buckets the page shows (proposed, unmatched external, unmatched ledger, matched, ignored, upcoming), opening_difference, unexplained_difference (0,00 by construction when data is consistent), dead-link handling (a link to a reversed/draft entry counts as unlinked and is flagged), awaiting_external for ledger lines within 5 days of the snapshot, staleness, and a window that scopes item lists without hiding older rows. Core reads skattekonto_transactions and the extension's snapshot row directly; no @/extensions import. - lib/reconciliation/gl-balance.ts: one ledger-balance helper with the trial-balance predicate status IN (posted, reversed). The drift check summed posted only, which misstated 1630 for any company with a storno on the account; skattekonto-drift.ts now delegates to the helper. - Proposals at sync: migration 20260823120000 adds suggested_journal_entry_id / suggested_at (ON DELETE SET NULL, partial index on open rows); the sync calls refreshSkattekontoProposals after the upsert. findMatchSuggestionsBulk now assigns one-to-one across rows (AGI period first, then nearest date) and falls back to an entry whose 1630 lines net to the amount (split lines); a proposal is never a link. - lib/reconciliation/service.ts + schemas.ts: the account-keyed facade (bank:<cash_account_id> | skattekonto | manual:NNNN) with listReconciliationAccounts (enabled cash accounts folded per IBAN, skattekonto when configured) and getAccountStatus dispatching to the bank engine or the new one; shared Zod shapes for the v1 registry, MCP schemas and the UI (PR 2). Tests: identity on a mixed fixture, storno pair, stale snapshot, awaiting window, window scoping, failed ledger read, live-linked entries never proposed; matcher one-to-one and split-line cases; proposal refresh writes/clears; service dedupe and dispatch. No UI in this PR. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix(reconciliation): roundOre instead of inline öre rounding (guard ratchet) The antipattern ratchet counts Math.round(x*100)/100; the new engine used it in five places. Switch to roundOre from @/lib/money and ratchet the baseline down by the three occurrences this removes net of the matcher rewrite. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * feat(reconciliation): three doors over one engine: dashboard routes, v1 API and MCP tools for account-keyed reconciliation PR 2 of the Avstämning build (design: Avstämning via API och MCP). Every door calls lib/reconciliation/{service,items,actions}.ts; none re-implements a link. - lib/reconciliation/items.ts: listAccountItems per account_key, the page's buckets (proposed, unmatched_external, unmatched_ledger, matched, ignored, upcoming), limit/offset; skattekonto from the engine, bank from the scoped transactions + unlinked GL lines (netted per entry). - lib/reconciliation/actions.ts: matchPairs (pairs or use_proposals, dry run, partial success with codes), unmatchLink, setItemIgnored; emits reconciliation.matched / reconciliation.unmatched. - lib/skatteverket/skattekonto-link.ts: canonical core link semantics for a skattekonto row (single line or entry net on 1630, live-link guard, race-safe update, unlink, ignore); the extension keeps its own matchSkattekontoToEntry until its tests are ported. - Dashboard routes /api/reconciliation/accounts[...]: list, status, items, links (POST), links/{linkId} (DELETE), items/{itemId}/ignore (POST); apply directly (a human clicked). - v1 routes /api/v1/companies/{id}/reconciliation/accounts[...]: same six, withApiV1, new scopes reconciliation:read / reconciliation:write (write is a staging scope for SoD), Idempotency-Key + dry_run on writes, registered for OpenAPI, load-routes, skills/accounted-api regenerated. Legacy bank routes and their transactions:* scopes unchanged. - MCP: gnubok_get_reconciliation_status takes account_key (legacy bank path untouched), new gnubok_list_reconciliation_items (default catalog), gnubok_reconcile_match (stages reconciliation_match, preflight = status) and gnubok_reconcile_unmatch (stages reconciliation_unmatch), both search-only to stay under the tools/list payload ceiling; gnubok_link_transaction_to_journal_entry moved to search. Executors in commit.ts; risk tiers medium/low; migration pair 20260823130000/130001 adds the two op types to the CHECK constraint (value list = live prod as of 2026-08-23 + the two); close_period loadout updated. Tests: service/actions/items/link unit tests, v1 route tests (401/403/400/404/ happy, idempotency, dry run), dashboard route tests, MCP tool tests + the guard suite (payload ceiling, descriptions, staging meta, qualified ids). Guards and apiskill:check green; no type errors in changed files. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix(reconciliation): refresh the v1 spec snapshot and keep the ignore update readable by the phantom-column guard The six new v1 reconciliation endpoints and the two new scopes were not recorded in the spec snapshot, and setSkattekontoRowIgnored updated through one conditional payload, which the phantom-column scanner cannot read (ceiling 380 -> 381). Two literal payloads instead; snapshot updated. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Jakob Wennberg <311770904+jakobwennberg-oss@users.noreply.github.com> Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
156 lines
6.0 KiB
TypeScript
156 lines
6.0 KiB
TypeScript
/**
|
|
* Recommended tool loadouts per workflow, surfaced by gnubok_get_agent_briefing
|
|
* as `recommended_tools`.
|
|
*
|
|
* Why: client harnesses with deferred tool loading (Claude Code ToolSearch,
|
|
* claude.ai connector search) otherwise burn 4-6 round-trips discovering tools
|
|
* cluster by cluster before any work happens. Each loadout names the exact
|
|
* registry tools a workflow needs, ordered by typical call sequence, so a
|
|
* harness that supports batch selection (ToolSearch select:a,b,c) loads the
|
|
* whole cluster in ONE call, and connector agents stop guessing search
|
|
* keywords.
|
|
*
|
|
* Drift protection (same spirit as deriveToolMeta): the loadouts are validated
|
|
* against the real tool registry and the workflow-skill registry via
|
|
* assertRecommendedLoadoutsValid(), called at module init in server.ts right
|
|
* after the tools array is defined. A loadout naming a tool or skill that does
|
|
* not exist fails module load, and therefore every test that imports the
|
|
* server. __tests__/agent-briefing.test.ts additionally pins the check.
|
|
*
|
|
* The list is static per issue #1098: the briefing does not currently query
|
|
* workflow state (unbooked counts, open periods), so gating inclusion on state
|
|
* would mean new reads in the hot bootstrap path. Every loadout is returned
|
|
* for every company; applicability is the agent's judgment call.
|
|
*/
|
|
import { workflowSkills } from './skills'
|
|
|
|
export interface WorkflowLoadout {
|
|
/** Stable snake_case workflow key (e.g. "categorize_month"). */
|
|
workflow: string
|
|
/** One-line English description of what the workflow accomplishes. */
|
|
description: string
|
|
/** Workflow-skill slug: pass to gnubok_load_skill for the full playbook. */
|
|
skill: string
|
|
/** Exact registry tool names, ordered by typical call sequence. */
|
|
tools: readonly string[]
|
|
}
|
|
|
|
export const RECOMMENDED_WORKFLOW_LOADOUTS: readonly WorkflowLoadout[] = [
|
|
{
|
|
workflow: 'categorize_month',
|
|
description: 'Categorize and book a month of bank transactions.',
|
|
skill: 'bank-reconciliation',
|
|
tools: [
|
|
'gnubok_list_uncategorized_transactions',
|
|
'gnubok_suggest_categories',
|
|
'gnubok_categorize_transaction',
|
|
'gnubok_match_transaction_to_invoice',
|
|
// For transactions whose affärshändelse is already booked on an existing
|
|
// verifikat: links without creating new bookkeeping. Categorizing such a
|
|
// transaction would double-book it.
|
|
'gnubok_link_transaction_to_journal_entry',
|
|
// Tagging: check the registry before writing dimensions bags on
|
|
// categorize calls (resolve-don't-select needs real codes/names).
|
|
'gnubok_list_dimensions',
|
|
'gnubok_load_skill',
|
|
'gnubok_approve_pending_operation',
|
|
],
|
|
},
|
|
{
|
|
workflow: 'close_period',
|
|
description: 'Reconcile, document voucher gaps, and lock a fiscal period.',
|
|
skill: 'month-end-close',
|
|
tools: [
|
|
'gnubok_list_fiscal_periods',
|
|
'gnubok_list_uncategorized_transactions',
|
|
'gnubok_get_reconciliation_status',
|
|
// Account-keyed reconciliation: the rows behind the bridge and the
|
|
// staged link (bank accounts and skattekonto alike).
|
|
'gnubok_list_reconciliation_items',
|
|
'gnubok_reconcile_match',
|
|
'gnubok_list_voucher_gaps',
|
|
'gnubok_explain_voucher_gap',
|
|
'gnubok_lock_period',
|
|
'gnubok_approve_pending_operation',
|
|
],
|
|
},
|
|
{
|
|
workflow: 'invoice_run',
|
|
description: 'Create and send customer invoices.',
|
|
skill: 'invoicing-rules',
|
|
tools: [
|
|
'gnubok_list_customers',
|
|
'gnubok_create_customer',
|
|
'gnubok_list_articles',
|
|
// Tagging: invoices carry default_dimensions + per-item bags; check the
|
|
// registry before setting them on gnubok_create_invoice.
|
|
'gnubok_list_dimensions',
|
|
'gnubok_create_invoice',
|
|
'gnubok_send_invoice',
|
|
'gnubok_mark_invoice_as_sent',
|
|
'gnubok_approve_pending_operation',
|
|
],
|
|
},
|
|
{
|
|
workflow: 'vat_declaration',
|
|
description: 'Compute, review, and file the VAT declaration.',
|
|
skill: 'quarterly-vat-review',
|
|
tools: [
|
|
'gnubok_get_vat_report',
|
|
'gnubok_vat_close_check',
|
|
'gnubok_get_general_ledger',
|
|
'gnubok_vat_declaration_validate',
|
|
'gnubok_vat_declaration_submit',
|
|
'gnubok_vat_declaration_status',
|
|
'gnubok_approve_pending_operation',
|
|
],
|
|
},
|
|
{
|
|
workflow: 'payroll_month',
|
|
description: 'Run monthly payroll and generate the AGI.',
|
|
skill: 'payroll-monthly',
|
|
tools: [
|
|
'gnubok_list_employees',
|
|
'gnubok_create_salary_run',
|
|
'gnubok_calculate_salary_run',
|
|
'gnubok_get_salary_run',
|
|
'gnubok_book_salary_run',
|
|
'gnubok_generate_agi',
|
|
'gnubok_approve_pending_operation',
|
|
],
|
|
},
|
|
]
|
|
|
|
/**
|
|
* Fails fast when a loadout references a tool or workflow skill that does not
|
|
* exist. Called at module init in server.ts (after the tools array is built)
|
|
* so any rename/removal in the registry breaks the build and the test suite
|
|
* immediately instead of shipping a briefing that recommends phantom tools.
|
|
*/
|
|
export function assertRecommendedLoadoutsValid(knownToolNames: ReadonlySet<string>): void {
|
|
const knownSkillSlugs = new Set(workflowSkills.map((s) => s.slug))
|
|
const seenWorkflows = new Set<string>()
|
|
for (const loadout of RECOMMENDED_WORKFLOW_LOADOUTS) {
|
|
if (seenWorkflows.has(loadout.workflow)) {
|
|
throw new Error(
|
|
`recommended_tools: duplicate workflow key "${loadout.workflow}" in RECOMMENDED_WORKFLOW_LOADOUTS.`
|
|
)
|
|
}
|
|
seenWorkflows.add(loadout.workflow)
|
|
if (!knownSkillSlugs.has(loadout.skill)) {
|
|
throw new Error(
|
|
`recommended_tools: workflow "${loadout.workflow}" references unknown skill slug "${loadout.skill}". ` +
|
|
'Update RECOMMENDED_WORKFLOW_LOADOUTS in recommended-tools.ts.'
|
|
)
|
|
}
|
|
for (const toolName of loadout.tools) {
|
|
if (!knownToolNames.has(toolName)) {
|
|
throw new Error(
|
|
`recommended_tools: workflow "${loadout.workflow}" references unknown tool "${toolName}". ` +
|
|
'Update RECOMMENDED_WORKFLOW_LOADOUTS in recommended-tools.ts when renaming or removing tools.'
|
|
)
|
|
}
|
|
}
|
|
}
|
|
}
|