Terminal Ops

When you need to fix something in a repo and prove you actually fixed it, this is the workflow. It's narrower than general coding help: you inspect first, make the smallest change that solves the problem, run the proving command, and report exactly what state things are in (changed locally, verified, committed, pushed). The guardrails are sensible: don't claim it's fixed until you reran the test, don't say you pushed unless the branch actually moved upstream, and don't turn a one-line fix into repo-wide churn. It pulls in other ECC skills like verification-loop and tdd-workflow when the fix needs real coverage. Good for CI failures, debug sessions, and anything where "trust me" isn't enough.