project: duplicate project rows for the same directory, and archiving is undone on re-resolve #61104

Summary

OpenCode creates multiple project rows for the same canonical directory, and archiving one does not stick. One row is keyed by the repo's first-commit hash; evicting/re-resolving the location creates a second row with a random ID. There is no API/CLI/UI to archive or delete a project, and when a row is archived directly in the database, re-resolving the location (e.g. after a restart) reactivates it.

Environment

• opencode version: 2.2.0
• OS: Windows_NT 10.0.26300 (win32 x64)
• Terminal: xterm-256color (OpenCode desktop app)
• Shell: pwsh configured; ComSpec C:\Windows\system32\cmd.exe
• Install/channel: desktop app, latest
• Active plugins: none

Reproduction

1. Have several git repositories under a directory tree and open each once so it registers a project (GET /api/location or by using it in the app).
2. Evict and re-resolve a location:
   • DELETE /api/debug/location?location[directory]=<dir>
   • GET /api/location?location[directory]=<dir>
3. GET /api/project now returns two entries with the same canonical but different id.
4. Archive the extra row — there is no API for it, so set time_archived in the project table — then restart OpenCode / re-resolve the location.

Expected Behavior

• Exactly one project per canonical directory.
• Re-resolving a location reuses the existing project instead of creating a new row.
• Archiving/deleting a project is supported and persists.

Actual Behavior

• Duplicate project rows per canonical directory. In one session, evicting + re-resolving each of 8 locations created 8 extra rows; a later reboot revived one archived row when its location was restored.
• Archiving is undone by re-resolution: after the reboot, the archived duplicate for the location that was restored became active again, while archived rows for locations that were never touched stayed archived.
• No supported way to remove or archive a project:
  • GET /api/project supports listing (with an archived filter), and PATCH /api/project/{projectID} accepts only canonical, name, icon, commands — no delete/archive.
  • The desktop app's project client exposes the same two operations.
  • The CLI has no project subcommand.

Additional Context

project table rows for a single directory (illustrative). The first id equals that repo's initial commit hash; the second is random:

id=ec38b3013dbcc4980ad0bc27905420e65743bfec  worktree=C:/lab/projects/home-assistant  vcs=git  name="Home Assistant Configuration"
id=bab03753f2112a6b2bd6f6a5673cdfc2f85232b8  worktree=C:/lab/projects/home-assistant  vcs=git  name=null

• Frequency: reproducible — a loop of evict + re-resolve over 8 directories produced 8 new rows; the reboot recurrence happened once when a previously-archived location was restored.
• Workaround: edit the SQLite project table directly (time_archived) to hide the extra rows. This is the only way found; it can be reverted by re-resolution.

total active: 17   total archived: 12
C:/lab/projects/home-assistant  -> 2 active rows (true duplicate)