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/@humanwhocodes/module-importer/README.md

@@ -0,0 +1,80 @@
+# ModuleImporter
+
+by [Nicholas C. Zakas](https://humanwhocodes.com)
+
+If you find this useful, please consider supporting my work with a [donation](https://humanwhocodes.com/donate).
+
+## Description
+
+A utility for seamlessly importing modules in Node.js regardless if they are CommonJS or ESM format. Under the hood, this uses `import()` and relies on Node.js's CommonJS compatibility to work correctly. This ensures that the correct locations and formats are used for CommonJS so you can call one method and not worry about any compatibility issues.
+
+The problem with the default `import()` is that it always resolves relative to the file location in which it is called. If you want to resolve from a different location, you need to jump through a few hoops to achieve that. This package makes it easy to both resolve and import modules from any directory.
+
+## Usage
+
+### Node.js
+
+Install using [npm][npm] or [yarn][yarn]:
+
+```
+npm install @humanwhocodes/module-importer
+
+# or
+
+yarn add @humanwhocodes/module-importer
+```
+
+Import into your Node.js project:
+
+```js
+// CommonJS
+const { ModuleImporter } = require("@humanwhocodes/module-importer");
+
+// ESM
+import { ModuleImporter } from "@humanwhocodes/module-importer";
+```
+
+### Bun
+
+Install using this command:
+
+```
+bun add @humanwhocodes/module-importer
+```
+
+Import into your Bun project:
+
+```js
+import { ModuleImporter } from "@humanwhocodes/module-importer";
+```
+
+## API
+
+After importing, create a new instance of `ModuleImporter` to start emitting events:
+
+```js
+// cwd can be omitted to use process.cwd()
+const importer = new ModuleImporter(cwd);
+
+// you can resolve the location of any package
+const location = importer.resolve("./some-file.cjs");
+
+// you can also import directly
+const module = importer.import("./some-file.cjs");
+```
+
+For both `resolve()` and `import()`, you can pass in package names and filenames.
+
+## Developer Setup
+
+1. Fork the repository
+2. Clone your fork
+3. Run `npm install` to setup dependencies
+4. Run `npm test` to run tests
+
+## License
+
+Apache 2.0
+
+[npm]: https://npmjs.com/
+[yarn]: https://yarnpkg.com/