remote-control rejects workspace trust set in .claude.json on Windows

Problem

claude remote-control says "Workspace not trusted" even though hasTrustDialogAccepted: true is correctly set in ~/.claude.json under the project path.

Environment

• Claude Code v2.1.81 on Windows Server 2022
• Running via SSH (non-interactive) and scheduled task
• Same trust mechanism works on Linux (devcontainer)

Steps to reproduce

1. Set hasTrustDialogAccepted: true in ~/.claude.json for a project path
2. Run claude remote-control --name test from that directory
3. Get: "Error: Workspace not trusted"

What was tried

• Setting full trust entry with all fields (allowedTools, mcpServers, etc.)
• Running from home directory (same error)
• Scheduled task (same error — not an SSH/TTY issue)
• claude -p "hello" --dangerously-skip-permissions works (skips trust check) but doesn't seed trust for remote-control
• --no-create-session-in-dir flag (same error)

Expected

remote-control should respect hasTrustDialogAccepted: true in ~/.claude.json, allowing headless/automated setup.

Context

We're building fleet orchestration where instances are set up programmatically. There's no way to run claude interactively on these headless Windows instances to accept the trust dialog.