fix(project): prefer existing sandbox project when remote URL changes

[bashrusakh]

Issue for this PR

Relates to #16995 (worktree cache lookup); not a direct fix for the per-worktree cache lookup itself, but a defense-in-depth fix that prevents the duplicate project / orphan sessions symptom whenever a directory's resolved project ID drifts (remote URL change, cache loss, worktree cache miss, etc.).

Type of change

• Bug fix
• New feature
• Refactor / code improvement
• Documentation

What does this PR do?

When the resolved project ID drifts away from an existing project whose sandboxes already contain this directory, reuse the existing project instead of upserting a new one. This covers:

• Remote URL change (e.g., after forking a repo) — projectV2.resolve computes a new ID from the new remote, but a worktree of the original project may already list this directory in its sandboxes.
• Worktree cache miss (related to Worktrees resolve to different project IDs due to per-worktree cache lookup #16995) — if a worktree falls back to a different ID because the per-worktree .git/opencode cache is missing, the sandbox match still routes the directory back to the canonical project.
• History rewrite / lost cache (related to Bug: orphan sessions when project id drifts after git history rewrite #30683) — the existing project survives the ID change rather than being shadowed by a new row.

Without this fix, fromDirectory either migrates the existing project to a new ID (causing the TUI to display a "fork" of the same project) or creates a duplicate row at the new ID, splitting sessions and emitting spurious (fork #1) sessions.

The lookup uses json_each on the sandboxes JSON column for a precise, case-sensitive match against the canonical git worktree path returned by projectV2.resolve — no full table scan, no LIKE on the serialized JSON.

How did you verify your code works?

• bun typecheck in packages/opencode — only pre-existing error in src/bus/global.ts
• bun test test/project/project.test.ts — 37/37 pass (added one new case for the sandbox-match reuse)
• bun test test/project/ in packages/opencode — 85 pass, 1 skip, 4 fail (all 4 failures are pre-existing on dev in instance.test.ts / instance-bootstrap.test.ts, unrelated to this change)
• bun typecheck and bun test test/project.test.ts in packages/core — clean

Screenshots / recordings

N/A (backend-only change)

Checklist

• I have tested my changes locally
• I have not included unrelated changes in this PR

[github-actions]

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

1. Open an issue describing the bug/feature (if one doesn't exist)
2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

[github-actions]

The following comment was made by an LLM, it may be inaccurate:

Potential Related PRs Found:

1. fix(opencode): preserve orphan sessions on project id drift #30682 - fix(opencode): preserve orphan sessions on project id drift

   • Directly related: addresses session orphaning when project IDs change, which is the downstream impact of the remote URL change issue this PR fixes.

2. fix(core): include git store hash in project ID to distinguish indepe… #29977 - fix(core): include git store hash in project ID to distinguish indepe...

   • Related: addresses project ID computation and distinction, which is part of the same problem space around project identity.

3. fix(project): repair split project IDs across worktrees #14287 - fix(project): repair split project IDs across worktrees

   • Related: addresses split project IDs across worktrees, which is a similar issue to the sandbox project reuse problem.

The current PR (#33594) fills a specific gap in sandbox project fallback handling mentioned in the notes section, complementing the earlier worktree cache fix via --git-common-dir.

[github-actions]

Thanks for updating your PR! It now meets our contributing guidelines. 👍