* fix: return to parent workspace when a fork is deleted remotely
When a workspace fork was deleted remotely while a user had it open,
reloading stranded them: a regular member got logged out (whoami fails on
the vanished workspace) and a superadmin silently landed on a dead
workspace whose requests 404. Detect the deleted fork on load and redirect
to its parent (or the workspace picker) with a toast instead.
- forkParentMemory.ts: persist a bounded fork->parent map in localStorage
while a fork is reachable (the parent is unrecoverable post-deletion).
- (logged) layout: record the current fork's parent via an effect.
- root layout: tryRecoverFromDeletedFork detects the vanished fork in
loadUser and redirects to the remembered parent or the workspace picker,
reusing the workspace list already fetched on mount.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* fix: verify fork existence for superadmins before deleted-fork redirect
* fix: only recover deleted fork on actual 404 from superadmin check
* fix: recover prefixless dev-workspace forks via remembered parent
* fix: use workspace exists check to detect deleted forks
* fix: restore wm-fork- detection for non-member superadmin forks
* fix: record fork parent for non-member superadmin dev workspaces
* Update frontend/src/routes/(root)/+layout.svelte
Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>
* fix: store fork parent map with null-prototype to handle __proto__ ids
---------
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>
