Booking via "Tidigare motparter" ended on a bare setExitingIds().add(id): the
row animated out of the inbox and that was the entire feedback. No "Bokförd"
toast, no Ångra, no unbooked-count decrement, and the id was never removed from
exitingIds again, so an undo would have restored the row's data while leaving it
filtered out of the list.
Extracted runCategorize's success tail into one finishBooking() rather than
copying the toast into the counterparty branch: the counterparty path was
already a second, thinner implementation of it, which is why it drifted. Both
paths and the counterparty activate-and-retry go through it now, pinned by a
parity test.
Also fixed on the way:
- handleTransactionBooked (manual booking dialog / voucher match) never
decremented the unbooked count, so the header read one too high until the
next refetch. It deliberately gets no Ångra: its `matched` branch links the
transaction to a PRE-EXISTING verifikat, and /uncategorize storno-reverses
whatever journal_entry_id the transaction points at.
- The 350ms animation timer re-applied the booked shape unconditionally, so an
Ångra resolving inside that window left the client claiming a journal_entry_id
the server had already storno-reversed. A completed undo now wins.
- finishBooking cleared processingId unconditionally; scoped to the finished id
so it cannot wipe an unrelated row's spinner.
No migrations.
Jakob Wennberg
954ce873a8