oikos-web: extract the client stack from dtoro/oikos

Phase 1 of the hexagonal-architecture plan (dtoro/oikos
plans/2026-08-15-hexagonal-architecture.md). Moves the delivery stack
for the control-room UI into its own repo with its own pipeline:

- web/ — Svelte 5 SPA, verbatim (vendor/ included)
- desktop/ — Wails v3 wrapper, updateURL repointed to
  dtoro/oikos-web releases
- compose/ — Dockerfile + Caddyfile, verbatim (the /wails/* 404 and
  asset no-fallback quirks are load-bearing)
- docker-compose.yml — single web service, same 8091:80 publish,
  mem/cpu limits, and restart policy as the oikos stack's web service
- scripts/deploy.sh — mirrors oikos deploy essentials: CI-green gate,
  TOCTOU guard, version-tagged oikos-web:v$VERSION, prune to 3
- cmd/webhook + scripts/install-webhook.sh — standalone push-to-deploy
  receiver on :9798 (env-only secrets, no Infisical dependency)
- CI: the web job from oikos's ci.yml + the desktop build/release
  workflow, path-adjusted

Own VERSION (0.33.0) with the same bump-on-main rule; starts above
oikos's 0.32.x so the desktop updater sees an upgrade.

web/vendor/examples/README.md

@@ -0,0 +1,18 @@
+# Orby runnable examples
+
+Serve the extracted download folder over HTTP, then open one of these files:
+
+- `canvas.html` mounts the native canvas engine and invokes semantic states.
+- `web-component.html` uses the browser-native `<joan-glyph>` element.
+- `state-sequence.html` runs, pauses, resumes, and restarts a timed sequence.
+
+For example:
+
+```sh
+python3 -m http.server 4173
+```
+
+Then visit `http://127.0.0.1:4173/examples/canvas.html`.
+
+Every import is relative to the files included in the kit. No package registry,
+bundler, framework, or third-party dependency is required.