feat: Phase 1 — extract the client (web SPA + desktop) to dtoro/oikos-web

Problem: the hexagonal refactor churns the backend tree for nine more
phases; the UI delivery stack (web/ SPA, cmd/desktop Wails wrapper,
compose/web image) must move to its own repo first so doc/layout
rewrites land once on a backend-only tree.

Change:
- New repo git.hubris.network/dtoro/oikos-web (v0.33.0): web/, desktop/
  (updateURL repointed to oikos-web releases), compose/, own CI (web +
  desktop jobs), own deploy script (CI-green gate, TOCTOU guard,
  version-tagged images, prune-to-3), own webhook receiver on :9798 +
  launchd unit, own compose project publishing the same 8091:80.
- Cutover executed on mac-mini in order: oikos stack's web service
  stopped+removed, oikos-web project brought up on 8091; outer Caddy
  untouched (targets the published port) — serving + Authentik flow +
  /wails 404 quirk verified post-cutover.
- Stripped from oikos: web/, cmd/desktop/, compose/web/, desktop CI
  workflow, ci.yml web job, Makefile ui/desktop/desktop-package/install
  targets, the compose web service, oikos-web from deploy.sh's fallback
  prune list; wails + go-keyring dropped from go.mod, vendor synced.
- README / CONTRIBUTING / AGENTS.md / .agents dev+operations docs now
  point at the new repo; mbse + mascot design docs carry a path note.

Risk: production SPA serving depends on the new pipeline now; rollback
is versioned-image re-up of the old web service from a pre-split
checkout (port 8091). Desktop builds installed before the split still
check dtoro/oikos releases — one manual reinstall, noted in the
oikos-web release notes.

Verification: go vet, make test (race), make generate-check, golangci
(no new findings; baseline down 400→365); post-cutover curls —
localhost:8091 200, /wails/runtime.js 404, outer Caddy 302 Authentik.

web/node_modules/runed/dist/kit/README.md

@@ -0,0 +1,35 @@
+# Runed Kit Utilities
+
+This subpath contains utilities that require SvelteKit to be installed.
+
+## Installation
+
+Make sure you have SvelteKit installed:
+
+```bash
+npm install @sveltejs/kit
+```
+
+## Usage
+
+```typescript
+// Import SvelteKit-dependent utilities from the kit subpath
+import { useSearchParams } from "runed/kit";
+
+// Regular utilities are still available from the main export
+import { isMounted, useEventListener } from "runed";
+```
+
+## Available Utilities
+
+- `useSearchParams` - Reactive URL search parameters management (requires SvelteKit)
+
+## Why a separate subpath?
+
+The main `runed` package is designed to work with Svelte alone, without requiring SvelteKit.
+However, some utilities like `useSearchParams` need SvelteKit's routing and navigation features. By
+providing these utilities through a separate import path, we ensure:
+
+1. The main package remains lightweight and SvelteKit-free
+2. SvelteKit users can access additional utilities when needed
+3. Clear separation of dependencies and requirements

web/node_modules/runed/dist/kit/index.d.ts

@@ -0,0 +1 @@
+export * from "../utilities/use-search-params/index.js";

web/node_modules/runed/dist/kit/index.js

@@ -0,0 +1 @@
+export * from "../utilities/use-search-params/index.js";

web/node_modules/runed/dist/kit/package.json

@@ -0,0 +1,9 @@
+{
+	"name": "runed-kit",
+	"private": true,
+	"type": "module",
+	"peerDependencies": {
+		"@sveltejs/kit": "^2.21.0",
+		"svelte": "^5.7.0"
+	}
+}