/wbDebug — ELI5

Your code is broken. Before you try to fix it, you want to know what's wrong. Not guess.

/wbDebug forces the AI to do what detectives do: look at the clues, form a theory, tell you the theory, and wait for you to check it before proposing a fix.

This matters because the fastest way to waste two hours is: see a red error → try a fix → still broken → try another fix → still broken → try a third fix. /wbDebug short-circuits that by making the AI explain its reasoning first.

Run it the moment you see an error you don't immediately understand. Not the third move — the first.

---