FSUtil.resolve aborts the calling fiber on non-NotFound realPath failure

Summary

FSUtil.resolve() only tolerated a NotFound failure from realPath; every other failure (for example PermissionDenied on an unreadable traversal component such as C:\System Volume Information on Windows, or ELOOP) escaped as a defect via Effect.orDie and killed the calling fiber.

The worst caller is the bash tool's external-command scan: it resolves every absolute-looking command argument before showing the permission prompt and documents those warnings as "advisory only". A single unreadable path in a command string (e.g. referencing a protected directory) aborted the entire tool with an opaque defect instead of degrading to the lexical path.

Expected

resolve() should best-effort canonicalize and, when canonicalization is impossible for any reason, fall back to the lexical path — consistent with its declared Effect.Effect<string> (no error channel) contract. The other callers (instruction discovery, project copy, repository cache) equally want a best-effort path, not a crash.

Actual

Any non-NotFound realPath error propagates through Effect.orDie, turning an advisory lookup into a fatal fiber defect.

Environment

• opencode version: dev
• platform: Windows (protected/system directories), also reproducible on POSIX with ELOOP / permission-denied paths