liquid swap not finished bc of asset mismatch, after upgrading peerswap to 5.0.1

A liquid swap got stuck for more than 10 hours, with
` "cancel_message": "invalid asset commitment got: 016d521c38ec1ea15734ae22b7c46064412829c0d0579f0a713d1c04ede979026f, expected 0a0a488de4899d0ae757f6cf8368663184d164106111ed9eaecf510e35282ddc6d",`

That is, it is still listed by `pscli listactiveswaps`, and I haven't received the coins.
Edit: The opening transaction has been confirmed 10 hours ago, and its output is still unspent (no redeem transaction).

Start by reproducing or tracing the stuck swap reported by pscli listactiveswaps, using the opening transaction and its invalid asset commitment error as the evidence. Compare the received and expected commitments through the swap lifecycle. Done means the asset mismatch is handled correctly and the swap either completes with a redeem transaction or is safely resolved.

Written by the indexing model from the issue text.