[Bug] macOS TCC re-prompts on every daemon update due to versioned binary paths

Bug Description
macOS TCC re-prompts after every auto-update for daemon-hosted sessions.
Sessions launched via /remote-control run under claude daemon run --origin transient -> --bg-pty-host, so TCC attributes them to the claude binary itself, not the terminal. tccd logs identifier_type=Path, responsible_path=~/.local/share/claude/versions/2.1.284. Every version bump = new path = new Desktop/Documents/Media Library prompts. System Settings > Files and Folders now lists 2.1.198 ... 2.1.284 as separate apps.
ClaudeCode.app/Contents/MacOS/claude is a hardlink to versions/2.1.284 (same inode), but TCC still records the versioned path, not the bundle id com.anthropic.claude-code.
Sessions launched directly in iTerm2 are unaffected (attributed to iTerm2).
Expected: a stable TCC identity across updates.

Environment Info

• Platform: darwin
• Terminal: iTerm.app
• Version: 2.1.284
• Feedback ID: 4a445080-612c-479b-9303-5150b24707c6

Errors

[]