Add "lessons/patterns/mcp_servers-field-in-pluginjson---another-failed-debug-theory"

lessons%2Fpatterns%2Fmcp_servers-field-in-pluginjson---another-failed-debug-theory.-.md

@@ -0,0 +1,40 @@
+## Context
+
+Plugins failing to load with "1 error" in Claude Code `/plugin` output.
+
+## Failed Theory
+
+Noticed that:
+- **Working plugins** (doc-guardian, git-flow, project-hygiene): NO `mcp_servers` field in plugin.json
+- **Failing plugins** (projman, pr-review, viz-platform): HAVE `mcp_servers` field in plugin.json
+
+Hypothesized that the `mcp_servers` field was causing validation failures.
+
+## Why This Was Wrong
+
+**NOT VERIFIED YET** - This was proposed as a solution without testing first. Adding to lessons learned preemptively because the pattern of proposing untested solutions has wasted hours today.
+
+## What Should Have Been Done
+
+1. Actually TEST removing the field from ONE plugin
+2. Restart Claude Code
+3. Check if it loads
+4. THEN report findings
+
+## Session Context
+
+This is the 7th failed solution proposed on 2026-02-02 for the same plugin load failure issue. Previous failed attempts:
+1. Version mismatch
+2. MCP venv symlinks (5 hour loop)
+3. Agent model field
+4. Command frontmatter missing
+5. Command name field missing
+6. Frontmatter check first
+7. mcp_servers field (this one)
+
+## Key Lesson
+
+**STOP PROPOSING SOLUTIONS. TEST FIRST. REPORT RESULTS.**
+
+---
+**Tags:** plugin-debugging, failed-solution, mcp_servers, wasted-time, test-first