Jakob WennbergandClaude Opus 4.8
c74b19df1b
* feat(reconciliation): close the bank-feed loop on voucher links and re-tag mis-typed opening balances
Two related fixes to bank reconciliation correctness:
1. Auto-reconcile on voucher link. Linking an invoice or supplier invoice to
an existing voucher previously advanced only the invoice — the bank
transaction that paid it kept sitting in the Transactions inbox with a null
journal_entry_id. linkInvoiceToVoucher / linkSupplierInvoiceToVoucher now
call autoReconcileTransactionForLinkedVoucher (lib/reconciliation), which
links the bank transaction to the same verifikat when exactly one unbooked
line matches it. Best-effort and post-commit: a failure here never fails the
link. The result surfaces reconciledTransactionId; the inbox row leaves the
list and the UI shows link_success_tx_reconciled.
2. Re-tag mis-typed opening balances. getReconciliationStatus and the GL-line
matching RPCs identify a cash account's ingående balans solely by
journal_entries.source_type='opening_balance'. Companies migrated from other
systems often booked the bank IB as an ordinary voucher (source_type
'import' or 'manual'), so it was never excluded and surfaced as a phantom
reconciliation difference equal to the opening balance. Adds:
- migration mark_entry_as_opening_balance: a GUC-gated carve-out in the
immutability trigger plus a SECURITY DEFINER RPC that validates the entry
(balance-sheet lines only, dated on a fiscal-period boundary), flips the
source_type, and writes an audit row — no blanket data sweep.
- POST /api/reconciliation/bank/mark-opening-balance + MarkOpeningBalanceSchema.
- BankReconciliationView action to trigger it from the IB diff.
The gnubok_create_voucher executor now accepts a typed is_opening_balance flag
and derives source_type='opening_balance' only after validating class 1/2 lines
on the period start, so new IBs land correctly typed.
Covered by lib/reconciliation auto-reconcile tests, voucher-executors tests,
and a mark-entry-as-opening-balance pg-real test.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* chore: rebrand gnubok → Accounted and prune swarm agent skills
Product rebrand and skills housekeeping. No runtime behaviour change.
Rebrand: replace user-visible "gnubok" with "Accounted" across docs, READMEs,
in-code comments, doc-site content, MCP skill/resource prose, and the
gnubok-mcp package description. The MCP resource URI scheme is moved gnubok://
→ Accounted:// consistently across resource registrations, the event-type
comment, and the resource/skill tests. Deliberately preserved as stable
identifiers (NOT rebranded): the gnubok-company-id cookie, gnubok_sk_ / gnubok_inv_
token prefixes, the gnubok-mcp npm bridge name, and the AGI <gem:Programnamn>
value (kept 'gnubok' per its source comment — it is the software identifier sent
to Skatteverket and must not churn across visual rebrands).
Skills: remove the 27 swarm-* agent SKILL.md atoms (no longer used; already
absent from the agent_atom_registry in prod), refresh the remaining skill docs,
add the .claude/rules/ path-scoped rule set, and regenerate the
seed_agent_atom_bodies migration + .skill-body-manifest.json via
`npm run skills:generate` so the DB-backed skill bodies match the trimmed set.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Modifier atoms
Cross-cutting attributes that aren't an industry on their own but change how the agent interprets the company. The composer can pick several modifiers per company.
.claude/skills/modifier/
├── README.md ← this file
├── single-shareholder-ab-fmb/
│ └── SKILL.md
├── enskild-firma/
│ └── SKILL.md
└── small-employer/
└── SKILL.md
When to author a modifier vs. a vertical
- Vertical = what the company does (restaurang, e-handel, konsult-IT).
- Modifier = a structural attribute (form, ownership, employer status, multi-currency, blandad verksamhet, …).
A company will typically have 0–1 vertical and 0–3 modifiers.
Authoring contract
Same SKILL.md + YAML frontmatter as industry/ atoms, but tier: modifier
and no sni_prefixes:
---
id: modifier/<slug>
tier: modifier
title: "Display name"
description: >
One paragraph the composer reads when deciding whether to load this.
Cover the qualifying conditions (e.g. "AB med en aktieägare") and the
most distinctive accounting implications.
trigger_signals:
ownership: "single_shareholder"
bas_account_patterns: ["2898", "2899"]
estimated_tokens: 6000
version: 1
---
Suggested body sections
- When this applies — the precise conditions the agent should look for.
- Implications — what changes in day-to-day bookkeeping.
- Regulatory edge cases — laws that fire because of this modifier.
- BAS account patterns — accounts that show up because of it.
- References — links to horizontals and into
references/*.mdfiles.
Adding / removing
Same workflow as industry/: write the SKILL.md, run
npx tsx scripts/seed-agent-atom-registry.ts. Set is_active: false to
deprecate.