Remote-session uploads from git worktrees handle per-worktree config differently

What

A git worktree is an extra checkout of the same repository in another folder. Such a checkout can have its own settings file, config.worktree, which git uses when extensions.worktreeConfig is turned on. When Claude Code packages a repository to send to a remote or cloud session, it checks for these settings.

• Detection now has three states: extension, inert (a config.worktree file that contains only harmless keys) and file. Before, there was a single yes-or-no check for the extensions.worktreeConfig extension.
• If the upload fails at the step that handles the worktree's administrative folder, the inert case now has its own explanation. It says that a per-worktree configuration file (config.worktree) stands in its administrative entry.
• The tamper check for linked worktrees is stricter. When the policy is "refuse", any worktree config state other than "absent" is treated as tampered. Before, only the "extension" state was refused.
• Upload diagnostics also record an inert_config worktree check.

Why

If you start remote sessions from a linked worktree, error messages are clearer when a config.worktree file gets in the way. More worktree setups may also be rejected as tampered during sync than before.