docs(roadmap): add gap closure phases 6-7

Phase 6 wires icon into .intunewin export (closes PKG-04).
Phase 7 fixes dashboard empty state and /packages 404 nav link.
PKG-04 reset to Pending in REQUIREMENTS.md traceability table.

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

.planning/REQUIREMENTS.md

@@ -41,7 +41,7 @@ Requirements for initial release. Each maps to roadmap phases.
 - [x] **PKG-01**: User can export a complete .intunewin package (script + drivers + detection + metadata)
 - [x] **PKG-02**: .intunewin is generated natively in Python (no IntuneWinAppUtil.exe dependency)
 - [x] **PKG-03**: User can export a NinjaRMM ZIP package (install script + driver folder)
-- [x] **PKG-04**: User can upload a custom PNG icon for Intune app display (256x256, max 750KB)
+- [ ] **PKG-04**: User can upload a custom PNG icon for Intune app display (256x256, max 750KB)
 - [x] **PKG-05**: User can preview and copy Intune install/uninstall command strings before export
 
 ### Infrastructure
@@ -108,12 +108,14 @@ Which phases cover which requirements. Updated during roadmap creation.
 | PKG-01 | Phase 5 | Complete |
 | PKG-02 | Phase 5 | Complete |
 | PKG-03 | Phase 5 | Complete |
-| PKG-04 | Phase 5 | Complete |
+| PKG-04 | Phase 6 | Pending |
 | PKG-05 | Phase 5 | Complete |
 
 **Coverage:**
 - v1 requirements: 27 total
 - Mapped to phases: 27
+- Satisfied: 26
+- Pending (gap closure): 1 (PKG-04)
 - Unmapped: 0
 
 ---