chore(docs): update .cursorrules

Author: JamieMason

.cursorrules

@@ -16,7 +16,7 @@ Before any work, read:
 
 - User intent unclear or multiple valid approaches exist
 - Breaking changes or core architecture modifications
-- Creating new files/modules not explicitly requested
+- Creating ANY new files/modules not explicitly requested (including docs, notes, examples)
 - Large refactors (ALWAYS ask strategy questions first)
 - Architectural decisions: HashMap keys, error handling, etc.
 
@@ -149,8 +149,11 @@ STOP if you think:
 - "I can refactor later if wrong"
 - "This is a minor detail"
 - "I'll create helpful documentation"
+- "I'll write a summary file"
+- "Let me document this implementation"
 
 Self-check: "Could this be done differently?" → Ask user
+Self-check: "Am I creating a file user didn't request?" → STOP
 
 ### Code Search: MUST use ast-grep for .rs files
 
@@ -180,7 +183,7 @@ Use grep/rg ONLY for: multiple file types, intentionally searching comments, non
 - Don't change: Public APIs (breaking)
 - Don't add: Dependencies without discussion
 - Don't remove: Tests
-- Don't create: Files unless explicitly requested
+- Don't create: Files unless explicitly requested (NO docs, notes, examples, summaries)
 
 ## Design Rationale