Bug: Editor fails to update workspace path cache after moving project folder out of OneDrive

[rsendres]

Describe the bug

When moving a project folder from a OneDrive-synced directory (e.g., ~\OneDrive\Desktop\MyProject) to a local root directory (e.g., C:/Project/MyProject/), the editor persistently retains and restores the old file path in the workspace metadata cache.

Even when explicitly closing the old folder, opening the new folder via the UI, or clearing the recent history, the interface reverts to showing the previous OneDrive path and fails to recognize the new location until multiple restarts and project closures are performed.

Steps to reproduce

1. Create or open a project located inside a OneDrive directory (e.g., ~\OneDrive\Desktop\MyProject).
2. Close the editor.
3. Move the project folder physically to a different partition or root path (e.g., C:\Project\ProjectName).
4. Launch the editor and use File > Open Folder to select the new path (C:\Project\ProjectName).
5. Notice that the editor UI still displays the old OneDrive path in the workspace header and fails to map the local files correctly.

Expected behavior

The editor should instantly flush the workspace path cache upon closing a folder or when a user explicitly loads a new directory via Open Folder, mapping the workspace context to the exact absolute path selected.

Environment

• OS: Windows 10 / 11 (with OneDrive active)
• Editor: OpenCode / Electron-based Workspace Environment

[ulises-jeremias]

I investigated this and prepared a fix.

Root cause appears to be stale project-root resolution in layout.tsx:

• projectRoot(directory) can return a root from serverSync.data.project based on persisted project metadata.
• After moving/renaming folders (for example OneDrive path -> local path), that metadata can still point to an old worktree path.
• Navigation then reuses the stale root and keeps restoring/reading session-route state under the old location.

Fix approach:

• In projectRoot(directory), only trust metadata-derived roots when they still match a currently known open project root.
• If metadata resolves to a stale/non-open root, fall back to the currently selected directory.

This prevents stale path restoration from hijacking navigation after folder moves.

I’m opening a PR with this change now.