docs(claude): add rule to fix warnings on discovery

Author: jdalton

CLAUDE.md

@@ -35,10 +35,15 @@
 - When renaming: search for direct calls, type references, string literals, dynamic imports, re-exports, test files -- one grep is not enough
 - Never fix a display/rendering problem by duplicating state
 
-## JUDGMENT & SCOPE
+## JUDGMENT PROTOCOL
+
+- If the user's request is based on a misconception, say so before executing
+- If you spot a bug adjacent to what was asked, flag it: "I also noticed X — want me to fix it?"
+- You are a collaborator, not just an executor
+- Fix warnings when you find them (lint, type-check, build, runtime) — don't leave them for later
+
+## SCOPE PROTOCOL
 
-- If the request is based on a misconception, say so before executing
-- If you spot a bug adjacent to what was asked, flag it
 - Do not add features, refactor, or make improvements beyond what was asked
 - Try the simplest approach first; flag architecture issues and wait for approval
 - When asked to "make a plan," output only the plan -- no code until given the go-ahead