TCC network-volume permission re-prompts on every update (binary path includes version number)

Each Claude Code update installs to a new versioned path:
~/.local/share/claude/versions/<version>/...

Because the binary isn't packaged as an .app bundle with a CFBundleName, macOS's TCC (Files and Folders / Network Volumes) permission dialog can't resolve a display name and falls back to showing the version-folder name itself — e.g. the dialog literally reads:

"2.1.214" would like to access files on a network volume.

Since TCC grants are tied to the specific binary path, and every update produces a new path (2.1.214 → 2.1.215 → ...), the network-volume permission grant does not carry over between versions. This means the "would like to access files on a network volume" prompt reappears on every single update for users who work with network-mounted volumes/shares — which given frequent releases is a recurring annoyance.

Suggested fix: Package the CLI as a proper .app bundle (or otherwise give the executable a stable CFBundleName/stable code-signing identity path) so TCC entitlements persist across version upgrades instead of resetting each time.

Repro:

1. Install/update Claude Code.
2. Run a command that touches a path on a mounted network volume (SMB/NAS//Volumes/...).
3. macOS shows a permission prompt naming the app after its version number instead of "Claude Code".
4. Repeat after the next update — permission must be re-granted.