Remote Control: session creation fails with 400 when git repo has remote origin URL

Description

claude remote-control fails to create initial sessions when the project's git repository has a remote origin URL configured. The bridge API returns HTTP 400 with source: Extra inputs are not permitted.

Steps to Reproduce

1. In a git repository with a remote origin (git remote add origin https://github.com/...):

``bash
claude remote-control --name "test" --spawn same-dir
``

1. Observe: Server shows Ready with Capacity: 0/32 — session pre-creation fails silently
2. The session does NOT appear in claude.ai/code

1. In a git repository without a remote origin:

``bash
claude remote-control --name "test" --spawn same-dir
``

1. Observe: Server shows Connected with Capacity: 1/32 — works correctly

Debug Log Evidence

Failing case (with remote origin):

[bridge:api] >>> {"machine_name":"...","directory":"...","branch":"main","git_repo_url":"https://github.com/user/repo.git","max_sessions":32,"metadata":{"worker_type":"claude_code"}}
[bridge] Session creation failed with status 400: source: Extra inputs are not permitted

Working case (without remote origin):

[bridge:api] >>> {"machine_name":"...","directory":"...","branch":"main","git_repo_url":null,"max_sessions":32,"metadata":{"worker_type":"claude_code"}}
[bridge:init] Created initial session session_xxxxx

Workaround

Temporarily remove the git remote before starting remote-control:

ORIG=$(git remote get-url origin)
git remote remove origin
claude remote-control --name "project" --spawn same-dir &
sleep 5
git remote add origin "$ORIG"  # restore after connection established

Environment

• Claude Code CLI: 2.1.101
• macOS: Darwin 25.3.0 (arm64)
• Claude Desktop App: 1.1617.0
• Node.js: v25.9.0

Impact

Any project with a GitHub remote configured cannot use Remote Control. This is a regression from the previous --remote-control flag behavior (which worked regardless of git remote configuration).