docs(06): create phase plan

.planning/ROADMAP.md

@@ -53,7 +53,11 @@ Plans:
   3. User passes `--config /path/to/custom.toml` and the tool uses that file; if the file does not exist, the tool exits with a clear error before capture begins
   4. User types `frequncy = 440` in their config file and the tool exits at startup with an error naming `frequncy` as an unrecognized key
   5. User sets waveform for one class in TOML and leaves all other classes at their defaults — the unspecified classes are unchanged
-**Plans**: TBD
+**Plans:** 2 plans
+
+Plans:
+- [ ] 06-01-PLAN.md — Config package: TOML load, validate, merge with TDD (config/config.go, config/config_test.go)
+- [ ] 06-02-PLAN.md — CLI wiring: --config flag, RunSynthesis signature change, main.go integration
 
 ### Phase 7: Custom Rules and Print-Config
 **Goal**: Users can define their own traffic classification rules in TOML, assign custom sounds to them, and inspect the full effective config before capture begins
@@ -75,5 +79,5 @@ Plans:
 | 3. Pipeline Integration and MVP | v1.0 | 2/2 | Complete | 2026-03-26 |
 | 4. Power User Features | v1.0 | 2/2 | Complete | 2026-03-26 |
 | 5. Waveform Types and Bank Decoupling | v1.1 | 2/2 | Complete   | 2026-03-26 |
-| 6. Config Package and Sound Overrides | v1.1 | 0/? | Not started | - |
+| 6. Config Package and Sound Overrides | v1.1 | 0/2 | Planning complete | - |
 | 7. Custom Rules and Print-Config | v1.1 | 0/? | Not started | - |