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/import-fresh/readme.md

@@ -0,0 +1,54 @@
+# import-fresh
+
+> Import a module while bypassing the [cache](https://nodejs.org/api/modules.html#modules_caching)
+
+Useful for testing purposes when you need to freshly import a module.
+
+## ESM
+
+For ESM, you can use this snippet:
+
+```js
+const importFresh = moduleName => import(`${moduleName}?${Date.now()}`);
+
+const {default: foo} = await importFresh('foo');
+```
+
+**This snippet causes a memory leak, so only use it for short-lived tests.**
+
+## Install
+
+```sh
+npm install import-fresh
+```
+
+## Usage
+
+```js
+// foo.js
+let i = 0;
+module.exports = () => ++i;
+```
+
+```js
+const importFresh = require('import-fresh');
+
+require('./foo')();
+//=> 1
+
+require('./foo')();
+//=> 2
+
+importFresh('./foo')();
+//=> 1
+
+importFresh('./foo')();
+//=> 1
+```
+
+## Related
+
+- [clear-module](https://github.com/sindresorhus/clear-module) - Clear a module from the import cache
+- [import-from](https://github.com/sindresorhus/import-from) - Import a module from a given path
+- [import-cwd](https://github.com/sindresorhus/import-cwd) - Import a module from the current working directory
+- [import-lazy](https://github.com/sindresorhus/import-lazy) - Import modules lazily