Introduce a three-tiered change classification (C0/C1/C2) based on the
Mikado method, where documentation cards serve as persistent context for
agents across sessions. Rename zk-docs to ai-docs. Add docs-mikado tool
to visualize active Mikado dependency chains.

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

@@ -0,0 +8,4 @@
+
+# Agent Change Process
+
+> **Audiences:** AI, Owner

@@ -0,0 +35,4 @@
+Use the [Mikado method](https://mikadomethod.info/) within a single session:
+
+1. Run `mise run ai-docs` to load context
+2. Attempt the change on a feature branch

@@ -0,0 +69,4 @@
+---
+title: Deploy Authentik
+status: active          # omit when complete
+requires:               # explicit dependencies

@@ -0,0 +92,4 @@
+
+- Single feature branch per C1/C2 change
+- Always revert broken working tree changes — don't leave broken code committed
+- Broken commits may happen (GitOps requires pushing to test) but must be reverted promptly

@@ -0,0 +3,4 @@
+# requires-python = ">=3.12"
+# dependencies = ["pyyaml>=6.0", "rich>=13.0.0", "typer>=0.15.0"]
+# ///
+#MISE description="View active Mikado dependency chains for C1/C2 changes"

@@ -0,0 +46,4 @@
+
+
+def build_graph() -> dict[str, dict]:
+    """Build the dependency graph from all docs."""