Remote sessions handle held messages and parked permissions better when you stop a turn

What

In a remote session, Claude Code sometimes holds back a message you send while it waits on something. A parked permission is a permission question that is waiting for an answer. A held message is one you sent that was kept back until that wait was over. This release changes what happens to both when you stop or rewind a turn:

• Interrupting or rewinding when there is no parked permission but there is a held message now marks that message as abandoned and reports it as stopped_before_run. Before, this case returned silently and the message could stay stuck.
• Interrupting while a permission is parked now ends the stopped turn for the client through endStoppedTurn, after the waiting permission is retired. Before, the transcript was updated but the client was never told the turn had ended. This only happens where parkedStopRetires is set, and a failure is logged as an error.
• A held message is now tracked across a parked answer, under the new remote capability ccr_parked_message_held, including a revoked_model_turn case.
• Duplicate-message checks gain a held_for_park case, and message admission gains a heldForParkedTurn hook.
• The remote session client no longer reports subscribers reported: false while the sender may not be attached yet.
• Cross-session hold receipts pass hidesFoldedNotices, and a system message marked interruptedBySendNow is now displayed.
• Session state now keeps per-main-thread contexts, spawned sets and parked teardowns. A new admit flag for project-person messages was also added.

The related gate tengu_resume_parked_permission has not been read, so whether this behaviour is active for any given account is unknown.

Why

Stopping a turn that was waiting on a permission, or that had a message queued behind it, could previously leave a remote session with a stuck message or a turn that never finished. These changes are aimed at making a stop or rewind leave the session in a clean state.