Code Cleanup

Structural cleanup, code-level cleanup, and refactoring — without breaking functionality.

Golden Rules

1. Preserve behavior — Every change must produce the same observable behavior. If you can't verify this, don't make the change.
2. Small incremental steps — One change at a time. Commit between steps. Never combine a refactor with a feature change.
3. Check existing conventions first — Before changing anything, read the codebase's existing coding guidelines, linting config, naming patterns, and file structure. Match them.
4. Test after each change — Run the test suite after every modification. If tests break, revert and try a smaller step.
5. Rollback awareness — Commit before starting. Note the hash. If a change chain gets too complex, git reset --hard <hash> and try a different approach.

Triage

Determine scope before starting. These parts can be used independently or combined.