docs(02-driver-management): create phase plan

Two plans: INF parser TDD (wave 1), upload endpoint + UI (wave 2).
Covers DRV-01 through DRV-05.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

.planning/ROADMAP.md

@@ -45,12 +45,11 @@ Plans:
   2. After upload, user sees a dropdown of driver names extracted from the INF (DriverDesc values), not a text field
   3. Uploaded driver packages survive container restarts (persisted to Docker volume)
   4. System flags files in the driver package that are not referenced by the INF, with a count or list
-**Plans**: TBD
+**Plans**: 2 plans
 
 Plans:
-- [ ] 02-01: Driver upload endpoint and volume storage (SHA256-keyed, deduplication)
-- [ ] 02-02: INF parser (DriverDesc extraction, multi-model INF support)
-- [ ] 02-03: Driver library UI (upload form, driver list, unused-file hints)
+- [ ] 02-01-PLAN.md — INF parser with TDD (encoding detection, token resolution, multi-model, unused files)
+- [ ] 02-02-PLAN.md — Driver upload endpoint, persistence, drivers page UI with HTMX
 
 ### Phase 3: Printer Configuration
 **Goal**: Technicians can configure all printer parameters, assign printers to clients, and retrieve saved configs without re-uploading drivers
@@ -109,7 +108,7 @@ Phases execute in numeric order: 1 → 2 → 3 → 4 → 5
 | Phase | Plans Complete | Status | Completed |
 |-------|----------------|--------|-----------|
 | 1. Foundation | 3/3 | Complete   | 2026-04-10 |
-| 2. Driver Management | 0/3 | Not started | - |
+| 2. Driver Management | 0/2 | Not started | - |
 | 3. Printer Configuration | 0/3 | Not started | - |
 | 4. Script Generation | 0/3 | Not started | - |
 | 5. Package Export | 0/3 | Not started | - |