list opencode sessions from every project, not just the serve's own

An opencode session in a git directory never appeared in /chat. The list read GET /session,
which answers for ONE project — the one the request's directory resolves to, and with no
x-opencode-directory header that is the serve's own cwd, DATA_PATH/opencode_server. Not a git
checkout, so it resolves to the catch-all project `global`, along with every other non-git
directory. That is why the default chat dir listed fine and nothing looked broken: a cwd that
IS a checkout gets its own project, and chat pwds are checkouts.

Measured on the live serve before changing anything: /session returned 8 sessions, /api/session
13, the five missing ones being an old project's. A session created in a git directory came back
0 times from /session and 1 from /api/session.

/api/session spans projects, so that is now the list. The per-id reads stay on /session — they
answer for any session regardless of project, verified 200 with and without the header.

The trap, and the reason listSessions normalises rather than returning the response: the two
surfaces disagree in silence. /session carries the working directory as top-level `directory`,
/api/session as `location.directory` with no top-level field, inside a {data: …} envelope.
Swapping the endpoint without the mapping leaves `directory` undefined on every session, which
the cwd filter turns into an empty list — the same shape as the metadata.officer.cwd bug this
filter already had once.

Verified against the live serve: with the mapping, a session in a git directory and one in the
general chat dir both resolve to their cwd, and every session carries a directory.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

src/servers/api/chat/opencode/client.ts

@@ -1,5 +1,7 @@
 // One connection per `opencode serve` base URL, for the REST reads the chat list and transcript need.
-// The SDK-style `/session/*` route family is used (feature-complete, incl. DELETE).
+// The SDK-style `/session/*` route family is used for the per-id reads and writes (feature-complete,
+// incl. DELETE) — those answer for any session regardless of project, verified 200 with and without a
+// directory header. The LIST is the exception and goes through `/api/session`; see `listSessions`.
 //
 // This used to also hold a shared SSE subscription (`GET /event`) demultiplexed per session, plus
 // `createSession`, `postMessage`, `abort` and `isServerHealthy` — the client half of a serve-based turn
@@ -12,10 +14,30 @@ class ServerConnection {
 
   // ── Session history (REST; OpenCode's SQLite store is the source of truth) ──
 
+  /**
+   * Every session the serve knows, across every project.
+   *
+   * `GET /session` — the endpoint this used — answers for ONE project: the one the request's directory
+   * resolves to, which with no `x-opencode-directory` header is the serve's own cwd
+   * (`DATA_PATH/opencode_server`). That directory is not a git checkout, so it resolves to the catch-all
+   * project `global`, and so does every other non-git directory — which is why the general chat dir
+   * listed fine and nothing looked wrong. A cwd that IS a git checkout gets its own project and its
+   * sessions were simply never returned. Measured on the live serve: `/session` 8, `/api/session` 13,
+   * and a session created in a git directory came back 0 times from `/session` and 1 from `/api/session`.
+   *
+   * Chat pwds are project directories, so that is the ordinary case, not the edge one.
+   *
+   * The two surfaces disagree about the shape, and the difference is silent: `/session` carries the
+   * working directory as top-level `directory`, `/api/session` as `location.directory` with no top-level
+   * field at all, wrapped in `{data: …}`. Normalised here so callers keep reading `directory` — reading
+   * the wrong one yields `undefined` for every session, which filters the list down to nothing.
+   */
   async listSessions(): Promise<OpenCodeSessionInfo[]> {
-    const res = await fetch(`${this.baseUrl}/session`);
-    if (!res.ok) throw new Error(`opencode GET /session → ${res.status}`);
-    return (await res.json()) as OpenCodeSessionInfo[];
+    const res = await fetch(`${this.baseUrl}/api/session`);
+    if (!res.ok) throw new Error(`opencode GET /api/session → ${res.status}`);
+    const body = (await res.json()) as { data?: ApiSessionInfo[] } | ApiSessionInfo[];
+    const sessions = Array.isArray(body) ? body : (body.data ?? []);
+    return sessions.map((s) => ({ ...s, directory: s.directory ?? s.location?.directory ?? null }));
   }
 
   /** One session's own record. The only place its working directory can be read on resume. */
@@ -72,6 +94,9 @@ export type OpenCodeSessionInfo = {
   directory?: string | null;
 };
 
+/** `/api/session`'s shape: the same record, with the directory one level down. Normalised by `listSessions`. */
+type ApiSessionInfo = OpenCodeSessionInfo & { location?: { directory?: string | null } };
+
 export type OpenCodeStoredPart = {
   type?: string;
   text?: string;