A document pinned to a transaction (transactions.document_id) with no
unconsumed inbox item was never anchored onto the verifikat when the
transaction was booked: document_attachments.journal_entry_id stayed
null and every underlag surface reported "Underlag saknas" for a
booking that HAS its underlag (attach-before-book via the manual
booking dialog, the 2026-08-13 user report).
PR #1547 already routed /book, bulk-book and categorize through the
shared propagateUnderlagForBookedTransaction helper, but that helper
only walked matched inbox items. This adds a pinned-document leg to the
helper, so all booking paths anchor the pin in one place:
- the pin is read fresh inside the helper (not from the caller's
pre-booking snapshot) so a concurrent attach is still anchored
- same guard semantics as inbox docs, via the extracted
anchorDocumentToJournalEntry: no-op when already anchored to this
verifikat, never steal another verifikat's underlag, log-and-continue
on failure (the booking is already posted; a re-run repairs the link)
- the bulk-book RPC already anchors pins atomically, so the leg no-ops
there
Route tests cover the three plan cases: pinned doc anchored, matched
inbox item stamped, and propagation failure never failing the booking.
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Mattsson
d9dddba682