Adapt GitOps bootstrap for private single-node Hetzner cluster

docs/04-app-of-apps.md

@@ -1,5 +1,18 @@
 # 04 — The app-of-apps pattern
 
+> **Current Hetzner deployment:** Application sources point to the public
+> `https://tea.ahmza.com/ahmza.com/vps-k8s.git` repository on `main`.
+> The app-of-apps explicitly selects only `demo.yaml` via
+> `spec.source.directory.include`; MetalLB and Longhorn remain unused
+> reference manifests, not automatic installs. The demo uses `ClusterIP`
+> (an internal-only Service address), reached via port-forward rather than
+> a public load balancer. In the steps below, commit and push the changed
+> manifests before applying the parent Application, and expect only `demo`
+> beneath it. Skip the LAN MetalLB/Longhorn phases for this setup. When
+> adding another app later, extend the parent's `include` filter too—for
+> example, `'{demo.yaml,new-app.yaml}'`. The three-app walkthrough below
+> describes the original LAN template, not this deployment.
+
 This is the last manual step. After this, Git drives everything.
 
 ## The idea