# Refactoring Roadmap

**Run**: 01-code-improvements
**Date**: 2026-03-28

## Execution Order

All 5 changes are grouped into a single phase (straightforward, low-to-medium risk).

| Priority | Change | Risk | Effort |
|----------|--------|------|--------|
| 1 | C05: Unify configuration | medium | 3 pts |
| 2 | C01: Update YOLO model | medium | 2 pts |
| 3 | C02: Replace external augmentation | medium | 3 pts |
| 4 | C03: Remove processed directory | medium | 3 pts |
| 5 | C04: Hard symlinks | low | 2 pts |

**Total estimated effort**: 13 points across 5 tasks

## Dependency Graph

```
C05 (config unification) ─── independent
C01 (YOLO update) ← C02 (built-in aug) ← C03 (remove processed dir) ← C04 (hard symlinks)
```

C05 can be done in parallel with the C01→C04 chain.

## Risk Mitigation

- Existing test suite (83 tests) provides safety net
- Each change committed separately for easy rollback
- C02 is the highest-risk change (training pipeline behavior change) — validate by running a short training sanity check after implementation
