fix

# Fix End-to-end fixing across the surfaces you actually work on: data pipelines, app stack, infra. Find the cause first, fix at the source, verify with fresh evidence, leave a regression guard so the same class of bug can't return. ## Iron law ``` NO FIX WITHOUT ROOT CAUSE. NO "DONE" WITHOUT FRESH EVIDENCE. ``` Symptom fixes are failure. Random changes waste time and create new bugs. Three failed attempts means the approach is wrong - stop and question architecture, don't keep trying. ## When to use | Surface | Triggers | |---|---| | **Data pipeline** | DAG/task failures, retry loops, dbt test failures, schema drift, freshness alerts, incremental/snapshot breakage, late or missing data | | **App backend** | 5xx, panics, deploy failures, failed migrations, env-var/secret mismatch, integration regressions | | **App frontend** | UI bug, weird behavior, hydration error, build failure, browser-specific regression, broken interaction | | **CI/CD** | failing GH Actions / pipeline jobs, flaky tests, build-matrix gaps, deploy gate failures, secret/env config drift | | **Terraform / IaC** | plan errors, apply failures, state drift, provider auth, cyclic deps, partial resources | | **K8s / cloud** | CrashLoopBackOff, OOMKill, image pull errors, networking/policy denial, secret rotation | | **Code-local** | type errors, lint issues, test failures, exceptions traced to a known file | ## Anti-patterns - stop if you catch yourself thinking this | Thought | Reality | |---|---| | "I ...