Keep reusable MMS sessions alive after connect-operation cancellation

[masarray]

Field failure reproduced from ARSAS

The fault-record scan succeeded, but starting Download cancelled the previous UI operation token. MmsClientSession had started its receive pump with that connection token, so the pump stopped while the session still reported MmsInitiated. The next FileOpen/FileRead then failed through stale confirmed-service routing, matching the observed first-chance sequence OperationCanceledException → InvalidOperationException → InvalidDataException.

Changes

• add an explicit API to rebind the receive pump from a short-lived connect/scan token to the MMS association lifetime
• refuse rebinding while confirmed operations are pending
• verify transport, association state and pump state after rebinding
• add a regression test proving that cancelling the completed connect-operation token no longer stops later confirmed responses

This does not change file filtering or COMTRADE interpretation. The transfer engine remains generic MMS FileOpen/FileRead/FileClose; COMTRADE grouping stays above the transport layer.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.