fix(transport): route order-bound notices by request id

[faysou]

Summary

• Preserve the originating request or order ID on Notice while keeping request‑less notices represented as None.
• Send order‑bound error frames to the order update stream as classified notices instead of raw error frames that an order decoder cannot represent.
• Classify code 399 as informational only when its message contains a line beginning with Warning:. Other code 399 messages remain order rejections.

flowchart LR
    TWS[TWS error frame] --> Decode[Decode error envelope]
    Decode --> Classify{Request ID and severity}
    Classify -- Order-bound warning --> Update[Order update stream: Notice]
    Classify -- Order-bound error --> Update
    Classify -- Request-scoped --> Request[Request subscription]
    Classify -- Request-less --> Global[Global notice stream]

Loading

Order consumers receive the request ID and severity without adding the intercepted error message type to any domain decoder.

Testing

• cargo test -p ibapi --features sync.
• Paper TWS forced‑rejection smoke: hard order errors remained terminal.
• Paper TWS code 399 smoke: a warning‑form stop order remained active and could be cancelled.

[wboayue]

Thanks @faysou — nice work. The 399 text-based classification and routing order errors to the update stream as typed notices are both solid improvements, and the paper TWS validation of both warning and rejection forms was exactly the right verification.

I pushed a few review follow-ups to your branch (9adbc1f): re-exported ORDER_MESSAGE_CODE (rustdoc gate was failing on the private link), changelog entries, doc updates showing how notices surface on order_update_stream (filter_data() drops them), and a small refinement so errors owned by data-request subscriptions don't get copied to the order-update stream. Will merge once CI is green.

[faysou]

Great, thank you. I did a refactor of the IB adapter in nautilus_trader but some changes belonged more naturally to rust-ibapi. Happy that these changes can be merged.