claude-code-autoconfig 1.0.101 → 1.0.102

package/.claude/updates/001-debug-methodology.md

@@ -17,13 +17,13 @@ The file lives at `~/.claude/projects/{encoded-project-path}/memory/MEMORY.md` w
 
 ```markdown
 ## Debugging — Evidence Before Solutions
-NEVER guess the root cause and jump to coding a fix. Ask yourself: is the cause deterministic and verifiable from the error alone?
-- **Deterministic means**: stack trace, compile error, or type error — NOT "I read the code and I think I see the issue." Reading code paths and reasoning about what "should" happen is a GUESS, not evidence.
-- If deterministic: fix it directly.
-- If NOT deterministic (this includes most runtime bugs):
-  1. Add logging / check actual data first
-  2. Confirm root cause with evidence
-  3. Only then propose and implement a fix
+
+**Never guess.** Before writing any fix, ask: do I have a stack trace, compile error, or type error that points directly to the problem?
+
+- **Yes** → Fix it directly.
+- **No** → Stop. Add logging first, get real runtime data, confirm the cause, *then* fix.
+
+"I read the code and I think I see the issue" is a guess, not evidence.
 
 **Circuit breaker — going in circles**: If the user reports your fix didn't solve the problem, STOP coding immediately. Add logging. No second guesses. Making another code change for the same symptom without new runtime evidence is going in circles.
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-code-autoconfig",
-  "version": "1.0.101",
+  "version": "1.0.102",
   "description": "Intelligent, self-configuring setup for Claude Code. One command analyzes your project, configures Claude, and shows you what it did.",
   "author": "ADAC 1001 <info@adac1001.com>",
   "license": "MIT",