Bug: click-to-jump fails when a repo has multiple Orca worktrees open with the same project name

[chelswcs]

Bug: click-to-jump fails when a repo has multiple Orca worktrees open with the same project name

Environment

• CodeIsland: v1.0.31 (Homebrew cask, wxtsky/tap)
• Host terminal: Orca (macOS app)
• macOS: Darwin 25.5.0 (Tahoe)

Steps to reproduce

1. In Orca, open the main worktree of a repo, e.g. bucket at /Users/me/Documents/claude/bucket.
2. In the same repo, open a second (child) worktree on a different branch, e.g. 1on1 at /Users/me/orca/workspaces/bucket/1on1. Both are live Orca terminal sessions running Claude Code at the same time.
3. In the CodeIsland notch panel, click the session card for the second worktree (1on1).

Expected
CodeIsland raises/focuses the exact Orca window/tab running that worktree's session (same behavior as a single-worktree repo).

Actual
Click-to-jump does not find the right window — it opens a new blank Terminal.app window instead of focusing the correct Orca pane.

Notes

• A single-worktree repo (e.g. pa-agent, only a main worktree open) jumps correctly every time.
• The failure only appears once a second worktree of the same repo is opened simultaneously. Both worktrees/windows share the same top-level project/repo name ("bucket"), which suggests the click-to-jump matcher is keying off project/repo name rather than the full worktree path, and can't disambiguate between the two live windows.
• This looks like the same class of issue already fixed for Cursor/Trae/Qoder/Factory per the changelog ("click-to-jump raising the most-recently-used window instead of the one running the clicked session — now matches the workspace window by project folder") — it seems the Orca integration may need the same full-path matching rather than project-name-only matching.

Happy to provide logs/socket traces if useful.