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/parent-module/readme.md

@@ -0,0 +1,67 @@
+# parent-module [![Build Status](https://travis-ci.org/sindresorhus/parent-module.svg?branch=master)](https://travis-ci.org/sindresorhus/parent-module)
+
+> Get the path of the parent module
+
+Node.js exposes `module.parent`, but it only gives you the first cached parent, which is not necessarily the actual parent.
+
+
+## Install
+
+```
+$ npm install parent-module
+```
+
+
+## Usage
+
+```js
+// bar.js
+const parentModule = require('parent-module');
+
+module.exports = () => {
+	console.log(parentModule());
+	//=> '/Users/sindresorhus/dev/unicorn/foo.js'
+};
+```
+
+```js
+// foo.js
+const bar = require('./bar');
+
+bar();
+```
+
+
+## API
+
+### parentModule([filepath])
+
+By default, it will return the path of the immediate parent.
+
+#### filepath
+
+Type: `string`<br>
+Default: [`__filename`](https://nodejs.org/api/globals.html#globals_filename)
+
+Filepath of the module of which to get the parent path.
+
+Useful if you want it to work [multiple module levels down](https://github.com/sindresorhus/parent-module/tree/master/fixtures/filepath).
+
+
+## Tip
+
+Combine it with [`read-pkg-up`](https://github.com/sindresorhus/read-pkg-up) to read the package.json of the parent module.
+
+```js
+const path = require('path');
+const readPkgUp = require('read-pkg-up');
+const parentModule = require('parent-module');
+
+console.log(readPkgUp.sync({cwd: path.dirname(parentModule())}).pkg);
+//=> {name: 'chalk', version: '1.0.0', …}
+```
+
+
+## License
+
+MIT © [Sindre Sorhus](https://sindresorhus.com)