cleanup

Author: KRRT7

.claude/rules/architecture.md

@@ -15,9 +15,14 @@ codeflash/
 ├── api/                    # AI service communication
 ├── code_utils/             # Code parsing, git utilities
 ├── models/                 # Pydantic models and types
+├── languages/              # Multi-language support (Python, JavaScript/TypeScript)
+├── setup/                  # Config schema, auto-detection, first-run experience
+├── picklepatch/            # Serialization/deserialization utilities
 ├── tracing/                # Function call tracing
+├── tracer.py               # Root-level tracer entry point for profiling
 ├── lsp/                    # IDE integration (Language Server Protocol)
 ├── telemetry/              # Sentry, PostHog
 ├── either.py               # Functional Result type for error handling
-└── result/                 # Result types and handling
+├── result/                 # Result types and handling
+└── version.py              # Version information
 ```

.claude/rules/source-code.md

@@ -5,7 +5,7 @@ paths:
 
 # Source Code Rules
 
-- Use libcst, not ast - always use `libcst` for code parsing/modification to preserve formatting.
+- Use `libcst` for code modification/transformation to preserve formatting. `ast` is acceptable for read-only analysis and parsing.
 - NEVER use leading underscores for function names (e.g., `_helper`). Python has no true private functions. Always use public names.
 - Any new feature or bug fix that can be tested automatically must have test cases.
 - If changes affect existing test expectations, update the tests accordingly. Tests must always pass after changes.