terminal-ops

Debug CI build failures by running minimum proving commands to inspect errors and git state first. This evidence-first terminal execution ensures changes remain narrow, testable, and audited before committing or pushing any repository modifications.

Evidence-first execution resolves the working surface like repo path and branch, then reads failing tests or errors before applying fixes. It requires inspecting before editing and rerunning proving steps to verify the exact terminal and git outcomes.

Verify a narrow git patch by rerunning the exact proving command that initially failed. The workflow mandates reading the failing surface first, applying a minimal fix, and executing verification steps to report precise execution outcomes.

Yes, you can inspect and push audited repository changes by selecting a mode like inspect, fix, verify, or push. The process resolves the branch and diff state, applies guardrails, and reports exact git push results in a standardized format.

Automated terminal fixes require strict guardrails and should not be used without inspecting the current git state first. Limitations include the necessity to rerun proving steps before claiming a fix and escalating changes only when a narrow patch is insufficient.