Initial commit: GitOps Starter Pack

A teaching-first, single-cluster GitOps setup: Talos Linux + Argo CD with
an app-of-apps layout, MetalLB pre-installed for real LoadBalancer IPs on
bare metal, a demo app, and a progressive docs/ walkthrough with a
CLAUDE.md tutor persona and guided bootstrap checklist.

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

talos/patch-controlplane.yaml

@@ -0,0 +1,15 @@
+# A patch applied on top of the controlplane.yaml that `talosctl gen config`
+# produces (see talos/README.md and docs/02-talos-bootstrap.md for the full
+# command). Talos's generated defaults assume a multi-node cluster where
+# control-plane nodes only run the Kubernetes control plane itself (API
+# server, scheduler, etcd, etc.) and never your actual workloads. For a
+# single-node learning cluster, that would mean nothing can ever be
+# scheduled — there's no other node to run it on.
+#
+# This one field undoes that restriction, letting the single node be both
+# the control plane AND a worker.
+#
+# >> Ask Claude: "why does Kubernetes normally keep workloads off control
+#    plane nodes?" if you want the reasoning before you turn it off.
+cluster:
+  allowSchedulingOnControlPlanes: true