TeamCreate agents: permission prompts route to terminal instead of remote-control UI

Bug Description

When running Claude Code with --remote-control (interactive mode, not the subcommand), team members spawned via TeamCreate that trigger permission prompts (e.g., WebFetch requiring approval) have those prompts routed to the physical terminal rather than the remote-control UI.

This causes the agent to block indefinitely waiting for permission approval that the user cannot see or interact with in their remote control interface.

Impact

• Agent becomes stuck mid-turn, unable to process any messages (including shutdown requests)
• TeamDelete fails because it requires all members to be shut down first (related: #31788)
• The only recovery is manual cleanup of team config directories
• In our case, a yin-outward research agent was stuck for ~20 minutes until we discovered the permission prompt on the wrong terminal

Steps to Reproduce

1. Start Claude Code with --remote-control flag (interactive mode)
2. Create a team with TeamCreate
3. Spawn a general-purpose agent as a team member
4. Have that agent perform a WebFetch (or any tool requiring permission approval)
5. Observe: permission prompt appears on the physical terminal, not the remote-control UI

Expected Behavior

Permission prompts from team member agents should route to the same UI surface the user is interacting with (the remote-control interface).

Environment

• Claude Code CLI (latest as of 2026-04-01)
• Running via --remote-control flag (interactive mode)
• Also possibly affects the remote-control subcommand (not confirmed)

Additional Context

Related to #31788 (TeamDelete blocked by hung agents) — permission routing issues are one cause of agents becoming unresponsive to shutdown requests. A --force flag on TeamDelete would mitigate the downstream impact even if the routing issue persists.