docs: move narrative wiki under knowledge/wiki/ (phase 3)

Problem: node and cross-cutting narratives lived at the repo root
(containers/, vms/, infrastructure/, host .md files), interleaved with the
machine-readable substrate.

Change:
- Move containers/ -> knowledge/wiki/containers/, vms/ -> knowledge/wiki/vms/,
  infrastructure/ -> knowledge/wiki/infrastructure/, hosts/{hubris,strong}.md ->
  knowledge/wiki/hosts/, infrastructure/references/ -> knowledge/sources/references/,
  GLOSSARY.md -> knowledge/GLOSSARY.md.
- Add knowledge/{index.md,log.md,sources/index.md} scaffolding.
- Rewrite all relative links repo-wide via a path-resolving mapper (inbound +
  outbound + between-moved-files), including .hermes/, runbooks, operations,
  investigations, plans, README, AGENTS.
- Repoint inventory.yaml doc_page fields and regenerate hosts/*.yaml (which
  embed doc_page); update oikos/gen-topology.py output path, candidate doc
  paths, and footer links; update code-comment doc paths.

Substrate untouched in place: inventory.yaml, hosts/*.yaml (regenerated,
idempotent), oikos/ code, mcp/, secrets/, bin/.

Verification:
- Logical broken-link set identical to pre-move baseline (net 128 -> 127; the
  topology regen fixed one, introduced none). Remaining are pre-existing refs
  to destroyed/archived nodes, out of scope for this move.
- gen-topology.py --check exit 0 (in sync); cards carry knowledge/wiki/ doc paths.
- build_host_files.py idempotent; all inventory doc_page targets resolve.
- MCP contract verified: get_page/search_docs/get_changelog resolve moved pages.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

knowledge/wiki/vms/108-haos.md

@@ -0,0 +1,44 @@
+# 108 — `haos-16.3`
+
+Home Assistant OS — the only VM on hubris (HAOS doesn't run cleanly in an LXC, hence the qm tenant).
+
+## At a glance
+- **Type:** QEMU VM
+- **HAOS version:** 16.3 (last verified)
+- **IP:** `192.168.8.101`
+- **Resources:** 4 GiB RAM, 32 GiB boot disk
+- **Public hostname:** [`home.hubris.network`](../infrastructure/dns.md) → [caddy (121)](121-caddy.md) → `192.168.8.101:8123`
+
+## Auth
+
+Native OIDC via the HACS integration `christiaangoossens/hass-oidc-auth` (repo `https://github.com/christiaangoossens/hass-oidc-auth`).
+
+Key gotchas:
+- HAOS containers don't honor the Network-panel DNS. Set Supervisor DNS via:
+  ```
+  ha dns options --servers "dns://192.168.8.180" --servers "dns://1.1.1.1"
+  ```
+  so OIDC discovery resolves internally to [authentik (124)](124-authentik.md).
+- Authentik app slug in the discovery URL is whatever was set in Authentik — confirm via the DB rather than guessing. User set `home-assistant` (with hyphen).
+- YAML config:
+  - `features.automatic_user_linking: true` — link to existing HA users by `preferred_username` match (otherwise a duplicate is created).
+  - `features.default_redirect: true` — skip the welcome-splash so users land on the normal HA login page.
+- Run `ha core restart` after each config change — HA caches DNS and OIDC discovery across frontend reloads.
+
+## Telemetry
+
+HA pulls Proxmox metrics via the official Proxmox VE integration. As of 2026-04-21 [claudio-monitor](../infrastructure/monitoring.md) stopped publishing to MQTT/REST (commit `82f0596`) — HA gets metrics from PVE directly; claudio-monitor focuses on alerting.
+
+## Related
+- [Authentik (124)](124-authentik.md)
+- [Caddy (121)](121-caddy.md)
+- [DNS](../infrastructure/dns.md)
+- [Monitoring](../infrastructure/monitoring.md)
+
+## Changelog
+
+### 2026-04-28 — wiki entry created
+Initial documentation.
+
+### 2026-04-21 — wired into Authentik via HACS hass-oidc-auth
+Supervisor DNS pointed at LXC 124 dnsmasq; YAML features for auto-linking + default redirect.