docs: consolidate documentation into organized structure

- Move 12 markdown files from root to docs/ subdirectories
- Organize documentation by category:
  • docs/troubleshooting/ (1 file)  - Technical troubleshooting guides
  • docs/deployment/      (4 files) - Deployment and security documentation
  • docs/guides/          (3 files) - Feature-specific guides
  • docs/planning/        (4 files) - Planning and improvement proposals

Root directory cleanup:
- Reduced from 16 to 4 markdown files in root
- Only essential project files remain:
  • CLAUDE.md (AI instructions)
  • README.md (Main project readme)
  • CLEANUP_PLAN.md (Current cleanup plan)
  • SRC_STRUCTURE_IMPROVEMENTS.md (Structure improvements)

This improves:
✅ Documentation discoverability
✅ Logical organization by purpose
✅ Clean root directory
✅ Better maintainability

phpstan-rules.neon

@@ -1,18 +1,24 @@
 rules:
     # Prefer Value Objects over arrays for domain concepts
     - App\Framework\Quality\PHPStan\Rules\PreferValueObjectsRule
-    
+
     # Use framework abstractions instead of direct PHP classes
     - App\Framework\Quality\PHPStan\Rules\UseFrameworkAbstractionsRule
-    
+
     # Forbidden PHP functions - enforce framework abstractions
     - App\Framework\Quality\PHPStan\Rules\ForbiddenFunctionsRule
-    
+
     # Time handling abstractions
     - App\Framework\Quality\PHPStan\Rules\UseClockAbstractionRule
     - App\Framework\Quality\PHPStan\Rules\UseTimerAbstractionRule
     - App\Framework\Quality\PHPStan\Rules\UseDateTimeAbstractionRule
 
+    # Naming Convention Rules
+    - App\Framework\Quality\PHPStan\Rules\Naming\ControllerNamingRule
+    - App\Framework\Quality\PHPStan\Rules\Naming\ExceptionNamingRule
+    - App\Framework\Quality\PHPStan\Rules\Naming\CommandNamingRule
+    - App\Framework\Quality\PHPStan\Rules\Naming\ValueObjectNamingRule
+
 parameters:
     # Type aliases for better documentation
     typeAliases: