Root Cause
Project name resolution has three related failure modes: (1) in monorepos/subdirectories, the git root is used instead of the cwd basename, silently losing context after upgrading; (2) worktree observations accumulate under a parent/leaf compound key, and the one-shot .cwd-remap-applied-v1 migration misses worktrees created afterward, orphaning them when the worktree is deleted; (3) sessions inside a git submodule resolve to the empty submodule leaf project rather than the parent repo, showing the empty-state banner despite rich history.
Tracked Items
Issues
PRs
Resolution
This is the canonical tracking issue for this root cause. Individual issues and PRs listed above will be closed in favor of this one.
Root Cause
Project name resolution has three related failure modes: (1) in monorepos/subdirectories, the git root is used instead of the cwd basename, silently losing context after upgrading; (2) worktree observations accumulate under a
parent/leafcompound key, and the one-shot.cwd-remap-applied-v1migration misses worktrees created afterward, orphaning them when the worktree is deleted; (3) sessions inside a git submodule resolve to the empty submodule leaf project rather than the parent repo, showing the empty-state banner despite rich history.Tracked Items
Issues
.cwd-remap-applied-v1migration; unreachable after the worktree is removed (v13.3.0) #2864 — Worktree observations orphaned by one-shot.cwd-remap-applied-v1migration; unreachable after the worktree is removed (v13.3.0) #2864PRs
Resolution
This is the canonical tracking issue for this root cause. Individual issues and PRs listed above will be closed in favor of this one.