safe-debug

When to apply

• The user provides a traceback, terminal error, or concrete training or inference failure symptom.
• The user wants diagnosis, root-cause narrowing, and minimal patch suggestions before code is changed.
• The user wants a safe debug flow with explicit human approval before mutation.

When not to apply

• When the user wants a broad repository walkthrough without an active failure.
• When the task is speculative experimentation or code adaptation.
• When the user is asking for a large refactor or readability rewrite.

Clear boundaries

• Diagnose first.
• Do not modify repository code by default.
• If a patch is needed, propose the smallest fix and require explicit approval first.