feat(frontend): typed openapi-fetch client over the generated schema

Main already generates frontend/src/api/schema.ts from the backend OpenAPI
document (#103) but ships only the types. This adds the thin runtime layer:
an openapi-fetch client typed by those generated paths, so the renderer makes
fully typed requests against the daemon's loopback /api/v1 surface instead of
hand-writing fetch calls.

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

Author: i-trytoohard

frontend/package-lock.json

@@ -9,6 +9,9 @@
     "typecheck": "tsc --noEmit",
     "start": "npm run build && electron ."
   },
+  "dependencies": {
+    "openapi-fetch": "^0.17.0"
+  },
   "devDependencies": {
     "electron": "^33.0.0",
     "typescript": "^5.6.0"

frontend/package.json

@@ -0,0 +1,11 @@
+import createClient from "openapi-fetch";
+import type { paths } from "./schema";
+
+// Typed client for the daemon's loopback /api/v1 surface. Request and response
+// types come from ./schema.ts, which is generated from the backend OpenAPI
+// document (`npm run api` at the repo root) — never hand-maintained.
+export const api = createClient<paths>({ baseUrl: "http://127.0.0.1:3001" });
+
+// Re-export the generated component schemas for convenient use in the renderer,
+// e.g. components["schemas"]["Project"], "Session", "APIError".
+export type { components, paths } from "./schema";