Persist and always consult worktree-to-repo maps for path exclusions

When an exclusion policy matches sessions by working directory and resolves linked git worktrees to their main checkout through the worktree's .git pointer file, record each worktree root and the checkout it belongs to, and consult that record on every check, not only once the directory is gone. Agent tooling deletes worktrees after a task, and paths get reused by unrelated directories. Periodic reconcilers re-evaluate held data later, so an unrecorded, removed, or recreated worktree no longer resolves and its held sessions upload. Key the record by worktree root and match by path prefix, so subdirectories never seen before are covered. Never evict entries. If the record can't be read, hold sessions; don't overwrite it. Where the agent records a repository remote, also match it against the excluded checkout's remotes, which covers worktrees removed before the exclusion existed. Limits: an unrecorded worktree with no remote evidence cannot be recognized, and a reused path stays excluded.

Applies when: a collector or sync tool excludes data by project path and agents work in short-lived git worktrees. Keywords: git worktree exclusion privacy opt-out reconciler deleted worktree commondir remote telemetry collector