Move to a three-node cluster with a Talos VIP; add Longhorn

Every node is now both control plane and worker, giving real tolerance
for losing any single machine (etcd quorum needs 3, not 1). A Talos VIP
gives the cluster one stable address regardless of which node answers.

Also pre-installs Longhorn for replicated storage, backed by a Talos
UserVolume on each node's second disk (>=900GB, non-system) rather than
the default path — mirroring the pattern from the homescale repo.

Docs renumbered to make room for 06-longhorn.md; checklist, glossary,
network map, and CLAUDE.md's guided-bootstrap instructions updated to
match, including asking the user for node IPs, VIP, and disk info before
generating any Talos config.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

apps/longhorn/Chart.yaml

@@ -0,0 +1,18 @@
+# An umbrella chart, same pattern as apps/metallb/Chart.yaml: it declares a
+# dependency on the upstream Longhorn chart and carries no templates of its
+# own — everything Longhorn needs (its CRDs, controllers, UI, default
+# StorageClass) comes from the dependency. See
+# docs/08-adding-new-apps.md for more on this pattern.
+apiVersion: v2
+name: longhorn-app
+description: Installs Longhorn, this repo's pre-installed distributed block storage
+version: 0.1.0
+dependencies:
+  - name: longhorn
+    # A version range rather than an exact pin — see the same note in
+    # apps/metallb/Chart.yaml. Check
+    # https://artifacthub.io/packages/helm/longhorn/longhorn for the
+    # current release and pin an exact version for a fully reproducible
+    # install.
+    version: ">=1.7.0"
+    repository: https://charts.longhorn.io