@kirjapro/mcp-server 0.12.0 → 0.14.0

package/CHANGELOG.md

@@ -1,5 +1,75 @@
 # Changelog
 
+## [Unreleased]
+
+## [0.14.0] - 2026-10-05
+
+Prepared, not yet published. Publish only after (1) `db:deploy` of the round-3
+migrations `20261005170000`–`20261005200000` (AI-työtila 2.0 batches 10–13;
+`kirjapro_send_invoice` needs `20261005180100`, the delivery intents), (2)
+`npm run functions:deploy -- dispatch-invoice` from the same main, which resumes a
+delivery under its intent, and (3) a commit of `src/database.types.ts` regenerated
+from production with `--schema public`, so `check:types-drift` passes. Until then
+0.13.0 keeps working unchanged against the current database.
+
+- `kirjapro_get_ar_aging` shares its result shaping with Kirjapro; an unexpected
+  report payload now returns a sanitized error instead of an internal exception.
+- `kirjapro_create_invoice`: `paymentTermDays` has no schema default any more, so
+  the customer's own payment term applies before 14 days (0.13.0 always used 14).
+  `vatRate` defaults to `25.5` only when a line has no `vatTreatmentCode`; an
+  explicit rate that contradicts the code is refused as `VAT_RATE_MISMATCH`
+  instead of the code winning silently. Lines take `discountPercent` (0–100, two
+  decimals, before VAT), and the historical `24`/`14` rates
+  (`legacy_standard_24` until 31.8.2024, `legacy_standard_14` until 31.12.2025)
+  are accepted inside their windows. Fingerprint changes.
+- `kirjapro_send_invoice` caches only a confirmed result. A lost transport, relay
+  error, 5xx or a delivery whose provider outcome is still pending returns
+  `IDEMPOTENCY_OUTCOME_UNKNOWN` and leaves the claim pending; 0.13.0 cached it as a
+  failure, which invited a retry with a new key. A confirmed refusal returns
+  `CODE: viesti` and a send returns `delivery_id`. Needs the database migration
+  `20261005180100` and the matching `dispatch-invoice` deploy (delivery intents).
+- The generated copies `src/compliance/purchase-vat-allocation.ts`,
+  `src/compliance/date-local.ts` and the new `src/shared/invoice-delivery.ts` are
+  byte-guarded by the test suite like `src/shared/invoice-draft.ts`.
+- `kirjapro_search_transactions` with `minAmount` or `maxAmount` returns
+  `FILTER_TOO_BROAD: …` when more than 1 000 transactions (or an unknown number)
+  match the other filters, instead of filtering only the first 1 000 and
+  reporting that sample's size as `total_count`. Up to 1 000 matches the count
+  stays exact. Narrow `dateFrom`/`dateTo` or `query` to search further.
+
+## [0.13.0] - 2026-10-04
+
+No database prerequisite: every function, rule and VAT treatment it uses was
+already live with 0.12.0, and 0.12.0 remains compatible with the same database.
+
+- `kirjapro_create_invoice` runs on the invoice-draft core that Kirjapro's AI
+  Chat also uses (`src/shared/invoice-draft.ts`, generated from the repository's
+  `src/lib/invoice-draft.ts`). Line amounts round like the database (numeric
+  `ROUND`, half away from zero), so 3 × 1.255 € returns 3.77 €, as stored;
+  0.12.0 returned 3.76 €.
+- The database allocates the invoice and reference number in the creation
+  transaction. The server no longer reads `get_next_invoice_number` first, and
+  the success message names the stored number.
+- Errors are a stable code with a Finnish explanation, `CODE: viesti` (for
+  example `VAT_REQUIRES_EU_VAT_NUMBER: …` or `FISCAL_YEAR_CLOSED: …`), like the
+  existing `IDEMPOTENCY_*:` errors. Other tools keep their English messages.
+- A lost database response returns `IDEMPOTENCY_OUTCOME_UNKNOWN` and leaves the
+  idempotency claim pending, so a retry with the same key never creates a
+  second invoice. 0.12.0 cached it as an ordinary failure.
+- When the invoice is created but reading it back fails, the result is a
+  success with a `warning` and the invoice id, cached like any success.
+- `paymentTermDays` must be a whole number of days (0–365). It still defaults
+  to 14, so the customer's own payment term applies only when it is passed.
+- Returned `lines` no longer echo `reverse_charge_confirmation_text`; the
+  database sets the invoice's confirmation text.
+- `kirjapro_send_invoice` declares `openWorldHint: true`: email and e-invoice
+  delivery are external effects. Only its fingerprint changes; the
+  `kirjapro_create_invoice` input schema and fingerprint are unchanged.
+- `kirjapro://compliance/vat`: the reverse-charge `implementation_limits` now
+  says that `kirjapro_book_purchase` takes `deductionPercent` 0–100 with a
+  documented reason, also for reverse charge. 0.12.0 still said that the
+  parameter did not exist.
+
 ## [0.12.0] - 2026-10-04
 
 Requires deployment of all seven migrations in the compliance batch before release: