[BUG] `claude remote-control` fails with 'Workspace not trusted' despite workspace being trusted in interactive mode

Description

claude remote-control (subcommand mode) always fails with "Workspace not trusted" error, even though the same directory is already trusted and works fine in interactive mode.

Steps to Reproduce

In the same directory (C:\Users\bossvibe):

1. Run claude → enters interactive session successfully (workspace is trusted)
2. Inside the session, run /remote-control → works fine ✅
3. Exit the session
4. Run claude remote-control --name "home" → fails ❌

Expected Behavior

claude remote-control should recognize the workspace as trusted, since claude (interactive mode) already trusts it.

Actual Behavior

C:\Users\bossvibe>claude remote-control --name "home"
Error: Workspace not trusted. Please run `claude` in C:\Users\bossvibe first to review and accept the workspace trust dialog.

Additional Context

• claude in the same directory works — no trust prompt
• /remote-control inside an interactive session works
• claude --remote-control also works
• Only the claude remote-control subcommand fails
• Issue persists after multiple re-trust attempts

Environment

• Claude Code: v2.1.78
• OS: Windows 11 Pro 10.0.26200
• Shell: cmd.exe / Git Bash
• Plan: Claude Max