From de24e1d18ea0c47c6ec8b88d28a028f77cfab89d Mon Sep 17 00:00:00 2001 From: Kawa Date: Mon, 13 Apr 2026 11:20:35 +0200 Subject: [PATCH] docs(phase-10): finalize Phase 10 plan list in ROADMAP --- .planning/ROADMAP.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.planning/ROADMAP.md b/.planning/ROADMAP.md index 0bf0aad..1b7d74a 100644 --- a/.planning/ROADMAP.md +++ b/.planning/ROADMAP.md @@ -64,7 +64,10 @@ Full details: [`milestones/v1.0-ROADMAP.md`](milestones/v1.0-ROADMAP.md) 3. After install, the Intune detection rule driven by the generated detect script reports "installed" for the endpoint 4. A technician triggering uninstall from Intune sees the printer cleanly removed from the endpoint under SYSTEM context 5. A reviewer can open `RUNTIME-VALIDATION.md` and read a signed-off report listing tenant, device, OS build, driver vendor(s), screenshots/logs, and any issues found -**Plans**: TBD +**Plans**: 3 plans + - [ ] 10-01-preflight-package-and-scaffold-PLAN.md — Generate real .intunewin from current commit and scaffold RUNTIME-VALIDATION.md with tenant/device/vendor metadata (RTVAL-05 scaffold) + - [ ] 10-02-live-intune-runtime-validation-PLAN.md — Drive RTVAL-01..04 manual checkpoints against a live Intune tenant + real Windows endpoint, capturing screenshots and device logs as evidence + - [ ] 10-03-report-signoff-PLAN.md — Finalize RUNTIME-VALIDATION.md, human sign-off, tick RTVAL-01..05 and mark Phase 10 complete ### Phase 11: Real-World Rollout & Feedback **Goal**: ImpTune is running in a real MSP environment, has produced a package that actually reached endpoints, and technician feedback has been captured and triaged.