docs(03): create phase plan for printer configuration

Two plans covering PRNT-01 through PRNT-10: printer+client CRUD with
Alpine.js port derivation (plan 01), and printer detail page with
regeneration placeholder (plan 02).

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

.planning/ROADMAP.md

@@ -60,12 +60,11 @@ Plans:
   2. Saved printer appears under its client/tenant label after page refresh
   3. System auto-populates the port name field from the entered IP address (user can edit it)
   4. User can open a saved printer config and regenerate its package without uploading the driver again
-**Plans**: TBD
+**Plans**: 2 plans
 
 Plans:
-- [ ] 03-01: Printer config form and CRUD API (all fields, validation, SQLite persistence)
-- [ ] 03-02: Client/tenant organization (label assignment, printer list grouped by client)
-- [ ] 03-03: Saved config retrieval and regeneration flow
+- [ ] 03-01-PLAN.md — Printer + client CRUD, form with all fields, Alpine.js port derivation, grouped list, integration tests
+- [ ] 03-02-PLAN.md — Printer detail page, saved config retrieval, driver association display, regeneration placeholder
 
 ### Phase 4: Script Generation
 **Goal**: The system produces correct, production-ready PowerShell scripts that handle all Intune and RMM execution contexts
@@ -109,6 +108,6 @@ Phases execute in numeric order: 1 → 2 → 3 → 4 → 5
 |-------|----------------|--------|-----------|
 | 1. Foundation | 3/3 | Complete   | 2026-04-10 |
 | 2. Driver Management | 1/2 | In Progress|  |
-| 3. Printer Configuration | 0/3 | Not started | - |
+| 3. Printer Configuration | 0/2 | Not started | - |
 | 4. Script Generation | 0/3 | Not started | - |
 | 5. Package Export | 0/3 | Not started | - |