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/tough-cookie/dist/cookie/defaultPath.d.ts

@@ -0,0 +1,40 @@
+import type { Nullable } from '../utils';
+/**
+ * Given a current request/response path, gives the path appropriate for storing
+ * in a cookie. This is basically the "directory" of a "file" in the path, but
+ * is specified by {@link https://www.rfc-editor.org/rfc/rfc6265.html#section-5.1.4 | RFC6265 - Section 5.1.4}.
+ *
+ * @remarks
+ * ### RFC6265 - Section 5.1.4
+ *
+ * The user agent MUST use an algorithm equivalent to the following algorithm to compute the default-path of a cookie:
+ *
+ * 1. Let uri-path be the path portion of the request-uri if such a
+ *     portion exists (and empty otherwise).  For example, if the
+ *     request-uri contains just a path (and optional query string),
+ *     then the uri-path is that path (without the %x3F ("?") character
+ *     or query string), and if the request-uri contains a full
+ *     absoluteURI, the uri-path is the path component of that URI.
+ *
+ * 2. If the uri-path is empty or if the first character of the uri-
+ *     path is not a %x2F ("/") character, output %x2F ("/") and skip
+ *     the remaining steps.
+ *
+ * 3. If the uri-path contains no more than one %x2F ("/") character,
+ *     output %x2F ("/") and skip the remaining step.
+ *
+ * 4. Output the characters of the uri-path from the first character up
+ *     to, but not including, the right-most %x2F ("/").
+ *
+ * @example
+ * ```
+ * defaultPath('') === '/'
+ * defaultPath('/some-path') === '/'
+ * defaultPath('/some-parent-path/some-path') === '/some-parent-path'
+ * defaultPath('relative-path') === '/'
+ * ```
+ *
+ * @param path - the path portion of the request-uri (excluding the hostname, query, fragment, and so on)
+ * @public
+ */
+export declare function defaultPath(path?: Nullable<string>): string;