desktop M10.3: frontend data-source adapter seam (repo interface + rest.ts)

Extract a typed repository interface (adapters/repo.ts) from the scattered
store/view -> api.* calls, backed by adapters/rest.ts (verbatim HTTP mapping)
and selected through adapters/index.ts. Every store and the notes-facing views
now depend on `repo`, never the HTTP client directly -- the seam the offline
local source (M10.5, over Tauri invoke) plugs into next.

Behavior-preserving for web: rest.ts maps each semantic method to the exact
endpoint the code called before; query-string and multipart building moved out
of the stores/views into rest.ts (the one place that knows the URL shape).
Client-side logic (reconcile/sort/optimistic reorder/toasts) stays in the
stores. GraphView + admin SettingsView keep direct api calls -- out of the
offline-core scope (M10.5 is board/editor/capture/search/filter/labels/
checklists/reminders).

Task 1992.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FRgehjoz7Yv8LkUfADxACm

frontend/src/stores/reminders.ts

@@ -1,6 +1,6 @@
 import { defineStore } from "pinia";
 import { ref } from "vue";
-import { api } from "../api/client";
+import { repo } from "../adapters";
 import router from "../router";
 import { useUiStore } from "./ui";
 import type { Note } from "./notes";
@@ -23,7 +23,7 @@ export const useReminderStore = defineStore("reminders", () => {
   // Single owner of the reminders endpoint — the RemindersView reads its list through
   // this too, so the URL + response shape live in one place.
   async function fetchReminders(): Promise<Note[]> {
-    return (await api.get<{ notes: Note[] }>("/api/notes/reminders")).notes;
+    return repo.notes.reminders();
   }
 
   async function check(): Promise<void> {