Mattsson 5769e35869 fix(api-v1): propagate underlag when booking via v1 categorize routes (#1564) ...

The v1 categorize and batch-categorize routes create the journal entry
via createTransactionJournalEntry directly and never ran the shared
underlag propagation, so a booking made through the API-key surface
left the transaction's pinned document unanchored and matched inbox
items unstamped: the same "Underlag saknas" gap #1560 closed for the
dashboard, /book and bulk-book paths, surviving on this one surface.

Both routes now call propagateUnderlagForBookedTransaction after the
CAS write succeeds (only when this request owns the booking; skipped on
partial success and lost CAS races). Best-effort by contract, same as
every other caller: a propagation failure is logged inside the helper
and never fails the booking.

Also adds the attach-after-bulk-book unit test salvaged from the closed
duplicate PR #1559: a document pinned to a bulk-booked transaction
(verifikat anchored via transaction_voucher_links) is anchored against
the samlingsverifikat when attached after the booking.

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

2026-08-13 13:48:01 +02:00

..

companies

fix(api-v1): propagate underlag when booking via v1 categorize routes (#1564)

2026-08-13 13:48:01 +02:00

health

style: remove em/en dashes repo-wide, add CLAUDE.md rule against them (#890)

2026-07-04 15:58:06 +02:00

openapi.json

style: remove em/en dashes repo-wide, add CLAUDE.md rule against them (#890)

2026-07-04 15:58:06 +02:00

operations/[id]

docs(api): correct /docs/api against the v1 implementation (#999)

2026-07-12 12:57:26 +02:00

webhook-deliveries/[id]/retry

feat(webhooks): dispatch on emit instead of waiting for the next cron tick (#1256)

2026-07-28 18:08:24 +02:00