Server crash (HTTP 500) when historical sandbox path is inaccessible (EACCES/PermissionDenied)

Description

When opening or connecting a new OpenCode instance, Project.fromDirectory validates existing project sandboxes using fs.exists(s).pipe(Effect.orDie).

If any historical sandbox path in the local SQLite database points to an inaccessible directory (for instance, a worktree created under another user with 0700 permissions, or an unmounted volume), Effect's fs.exists(s) fails with PlatformError: PermissionDenied: FileSystem.access.

Because Effect.orDie is applied, this turns into an unhandled fatal defect and crashes the local server request with HTTP 500:

Error: Unexpected server error. Check server logs for details.
    at <anonymous> (/$bunfs/root/chunk-etyajq96.js:8:7615)

Log trace:

level=ERROR message=failed error="PlatformError: PermissionDenied: FileSystem.access (/inaccessible/path) (cause: Error: EACCES: permission denied)"
    at Project.fromDirectory
    at InstanceStore.boot
    at InstanceStore.load

OpenCode version

1.18.31

Steps to reproduce

1. Have a sandbox path referenced in SQLite that is inaccessible to the current user (e.g. restricted permissions or unmounted volume).
2. Launch opencode in another repository or open a concurrent session.
3. Server throws HTTP 500 on boot when InstanceStore.load calls Project.fromDirectory.

Operating System

Linux

Start at Project.fromDirectory, then follow the InstanceStore.boot and InstanceStore.load path described in the trace; inspect how historical sandbox paths are read from SQLite and how fs.exists errors are handled. Reproduce with an inaccessible path, and consider the issue done when that condition no longer produces an unhandled defect or HTTP 500 during server boot.