kms: revert files accidentally bundled into the docs commit

The previous commit (81a7d804) swept in 23 unrelated working-tree files because
a rebase --autostash had left them staged in the index — including 4 files with
leftover git conflict markers (llama-cpp/main.tf, excalidraw/providers.tf,
url + wealthfolio .terraform.lock.hcl) from a stale 2026-05-25 stash, which is
invalid Terraform. Revert all 23 (terragrunt-generated backend/providers/lock
+ the llama-cpp markers) to their prior committed state; terragrunt regenerates
the generated files on the next run. Net effect of the docs commit is now just
the runbook doc.

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

stacks/llama-cpp/main.tf

@@ -280,19 +280,12 @@ resource "kubernetes_deployment" "llama_swap" {
   # for it to be reachable".
   wait_for_rollout = false
   spec {
-<<<<<<< Updated upstream
     # Restored to 1 on 2026-05-29 (was 0 during 2026-05-25 IO-storm recovery —
     # see docs/post-mortems/2026-05-25-immich-anca-elements-io-storm.md). The
     # immediate trigger was fire-planner's examples ingest needing qwen3-8b for
     # bulk Reddit-post extraction; only frigate is currently on the GPU on
     # k8s-node1 so contention is minimal.
     replicas = 1
-=======
-    # TEMP-SCALEDOWN-2026-05-25-IO-STORM: scaled to 0 during cluster recovery.
-    # Restore to 1 when cluster is fully stable. See post-mortem
-    # docs/post-mortems/2026-05-25-immich-anca-elements-io-storm.md.
-    replicas = 0
->>>>>>> Stashed changes
     strategy { type = "Recreate" }
 
     selector {