Much more detailed refusal messages for uploading/capturing an untrustworthy git checkout

When Claude Code hands a working copy of your repository off to a remote session (for example through bridge/remote control features that upload or capture your checkout), it now gives a specific, worded explanation when it refuses to do so because the checkout looks untrustworthy. Cases include:

• the .git entry being a symbolic link (which the session could re-point elsewhere)
• the .git entry being a hard link
• use of "reftable" storage for git references
• objects borrowed from another repository
• a nested repository inside the checkout
• worktree-specific config
• git config injected via environment variables

Each case now gets a plain-language sentence explaining why the session refuses to proceed and what to do instead, such as starting from an ordinary clone.