Remote Control disconnects when org policy starts refusing it, plus SDK bridge changes

What

Remote Control lets you drive a Claude Code session from somewhere else through a bridge, a connection that relays messages between the two. Claude Code now reacts when your organisation's policy changes while a bridge is running.

• Both the standalone claude remote-control loop and the bridge inside an interactive session watch for org policy changes.
• If policy now refuses Remote Control, the bridge shuts down or disconnects and shows a notice. The log line reads "Org policy now refuses the attached bridge".
• The standalone loop also holds a session whose minimum version has not arrived yet, refreshes its settings from the server, and then admits or declines it.

The SDK bridge also changed. The SDK is the kit for driving Claude Code from your own program.

• SDK MCP servers can be disabled and enabled through mcp_toggle. MCP servers are connectors that give Claude extra tools.
• The logic that reconnects after signing in again was reworked.
• The startup message (system/init) now includes messagesInView.

Why

Before, a policy change did not affect sessions that were already connected. Now, if your organisation turns off Remote Control, an active connection can end partway through, and a notice tells you why.