latest

fix(mbtool): parse the MSGID kludge the same way as REPLY and TZUTC

MSGID was cut at a fixed offset past the separator while REPLY and TZUTC are
cut from the separator itself and trimmed. On a kludge without a space after
the colon the first character of the MSGID was eaten, on one with extra or
trailing whitespace the spaces were kept.

Both sides of the parent lookup are compared for exact equality, so the
asymmetry alone was enough to leave a reply unlinked, silently. The stored
MSGID is also written back into the destination base verbatim, so a damaged
value was carried over into the new base.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>