Incoming ComStar Read Now prompt disconnects the client

[gnummers]

Description

Reading an incoming ComStar message disconnects the MPBT client instead of opening the message body.

Steps to Reproduce

1. Start mpbt-server@0.1.50.
2. Connect with the retail MPBT v1.23 client.
3. Send a ComStar message to an online pilot (this also reproduces by sending a message to yourself).
4. Accept the Incoming ComStar message\Read now? prompt.
5. Observe that the message body never opens and the client drops shortly afterward.

Expected Behavior

Choosing Read now should open the ComStar message body, mark the message read, and keep the client connected.

Actual Behavior

The server sends the incoming-message Cmd20 prompt, the client replies with cmd-7 listId=7 selection=1, the server ignores that reply as an unsupported list id, and no Cmd36 message-view packet is sent. The client then disconnects a few seconds later.

Environment

• Node.js version: v24.14.1
• OS: Windows_NT
• MPBT client patch level: v1.23 retail client

Priority

High — major functionality broken, no workaround

Additional Context

• Live packet capture: captures\1776470447231_80b68257-df50-4467-80fa-857bc13c9a3b.txt
• Correlated server log shows [world] cmd-7 menu reply: listId=7 selection=1 followed by [world] cmd-7 ignored: unsupported listId=7.
• Local fix moves the prompt handler onto the cmd-7 menu dispatcher and treats selection === 1 as Read now, which matches the live client reply.