Remote-control: "Allow for session" permission response locks up the session

Bug Report

Description

When using the Claude mobile app's remote-control feature to control a Claude Code session, responding to a permission prompt with "Allow for session" causes the session to lock up and become unresponsive. The session must be killed and restarted from the local machine to recover.

Steps to Reproduce

1. Start a Claude Code session on a desktop machine
2. Connect to it from the Claude Android app via the remote-control feature
3. Trigger a permission prompt (e.g. run a Bash command not in the allow list)
4. In the mobile app's native permission UI, tap "Allow for session"
5. Session locks up — no further responses, requires kill/restart from local machine

Expected Behavior

"Allow for session" grants the permission for the current session and the conversation continues normally, the same as "Allow once" does.

Actual Behavior

The session hangs indefinitely after tapping "Allow for session". The conversation becomes unresponsive. Only a kill from the local machine recovers it.

Additional Notes

• "Allow once" works correctly — the permission is granted and the session continues
• "Allow for session" consistently causes the lockup
• This appears to be a bug in how the remote-control bridge handles writing session-level permission state

Environment

• Platform: Android (Claude mobile app)
• Feature: Remote-control (/remote-control)
• Claude Code: CLI session on Linux (Arch Linux)