desktop: bundled sidecar (next-17403) crashes with 'Path is not absolute: global' — all API 500s, failed to load sessions #42266

Summary

OpenCode Desktop beta (Windows) can no longer load sessions after updating to the 0.0.0-next-17403 bundled sidecar. The sidecar server crashes on every database query with Error: Path is not absolute: global (and empty path), returning HTTP 500 for all /api/* endpoints — the app shows "Failed to load sessions" and sent user messages never appear in the chat transcript.

Environment

• opencode version: 0.0.0-next-17403 (bundled sidecar CLI), desktop app v0.0.0-beta-17402
• OS: Windows 10.0.26200 (win32 x64)
• Terminal: OpenCode Desktop app (Electron beta build)
• Shell: C:\WINDOWS\system32\cmd.exe
• Install/channel: beta / next
• Active plugins: claude-mem.js (local), opencode-see-image@1.3.0

Reproduction

1. Update desktop to the build that bundles CLI 0.0.0-next-17403 (sidecar at %APPDATA%\ai.opencode.desktop.beta\cli\0.0.0-next-17403\).
2. Launch OpenCode Beta.
3. The bundled sidecar starts (serve --service) and every request fails with HTTP 500; UI shows "Failed to load sessions".

Expected Behavior

Sessions load and the chat works as before (worked fine on the previous build 0.0.0-next-17400).

Actual Behavior

Server log (run e313a592, role=server) shows the sidecar crashing on the "global" project DB path:

Error: Path is not absolute: global
    at GN (../core/src/database/path.ts:19:15)
    ...
    at Project.resolve (../core/src/project.ts:102:14)
    at ServerProcess.start (src/server-process.ts:73:29)

and for the project insert:

Error: Path is not absolute:
    at GN (../core/src/database/path.ts:19:15)
    ...
    at Project.resolve (../core/src/location.ts:24:39)

All endpoints then 500: /api/session (causes the "failed to load sessions" toast), /api/agent, /api/project/current, /api/command, /api/mcp, /api/model, /api/provider, /api/location, /api/permission/request, /api/question/request.

A server running the previous build (0.0.0-next-17400, same serve --service startup, same projectID=global refresh) worked fine, so this is a regression introduced in 17403.

Secondary symptoms on the same desktop beta:

• The client occasionally calls GET /api/session/<id>/message with limit=0, which the server rejects with HTTP 400 (Expected a value greater than or equal to 1, got 0) — sent user messages then never render in the transcript even when the server is healthy.
• The claude-mem.js plugin now fails to load on the new server: SchemaError(Expected object, got async (t) => ...).

Additional Context

• Data is intact: session/message data verified present in ~/.local/share/opencode/opencode.db (via API on a healthy 17400 service instance).
• The old 17400 service process kept running alongside; the desktop connects to its own broken 17403 sidecar instead.
• Recurs consistently after restart; opencode2 service restart does not fix it (desktop relaunches the broken sidecar).