ImpTune/.planning/phases/10-real-world-runtime-validation/RUNTIME-VALIDATION.md

Runtime Validation Report — ImpTune v1.1

Status: IN PROGRESS — RTVAL-01 PASS on re-test (2026-04-13) against fixed build; plan 10-02 resumed at Task 2 (RTVAL-02 on-device install) Started: 2026-04-13 Signed off by: Signed off date:

Tenant & Environment

Field	Value
Intune tenant (domain)	rubis.fr
Test device hostname	ARES-5CG5220YTM
Windows OS build	26200.7171
Device is Intune-managed	yes
Driver vendor(s) tested	ricoh.zip

• PCL6 Driver for Universal Print | | ImpTune commit SHA | 00b709d25a | | Package file name | Copieur_2eme.intunewin | | Package SHA256 | 8818124aa97ed3da24bf73a1f08f43065e6efea46f44a3abffc9983b097d3ddc | | Generated at | 2026-04-13 |

RTVAL-01 — Tenant ingestion

Status: PASS Tested: 2026-04-13 (re-test against fixed build) Evidence:

• evidence/rtval-01-tenant-upload.png — Intune Win32 app wizard with parsed .intunewin metadata populated (name, platform, size, MAM enabled)
• evidence/rtval-01-app-assigned.png — app assignment screen showing the test device group Notes: Initial run on 2026-04-13 failed with empty wizard fields and greyed-out OK button (see ISSUE-01). Root cause was two structural defects in the .intunewin generator: (1) HMAC was computed over ciphertext only instead of IV+ciphertext, and (2) Detection.xml did not match the IntuneWinAppUtil.exe reference format. Both fixed in commits 74535ea and 7716246. Re-test on the fixed build against live tenant rubis.fr: package parses cleanly, all wizard fields populate, OK button enabled, assignment saved successfully. Package tested: Copieur_2eme.intunewin (SHA256 8818124aa97ed3da24bf73a1f08f43065e6efea46f44a3abffc9983b097d3ddc, ImpTune commit 00b709d)

RTVAL-02 — Install under SYSTEM (pnputil + $PSScriptRoot)

Status: BLOCKED — depends on RTVAL-01 PASS; RTVAL-01 returned FAIL (Intune cannot parse generated .intunewin). Cannot proceed until package structure defect is resolved. Evidence: (none — test not reached) Notes:

RTVAL-03 — Detection rule reports Installed

Status: BLOCKED — depends on RTVAL-01 PASS; RTVAL-01 returned FAIL (Intune cannot parse generated .intunewin). Cannot proceed until package structure defect is resolved. Evidence: (none — test not reached) Notes:

RTVAL-04 — Uninstall under SYSTEM

Status: BLOCKED — depends on RTVAL-01 PASS; RTVAL-01 returned FAIL (Intune cannot parse generated .intunewin). Cannot proceed until package structure defect is resolved. Evidence: (none — test not reached) Notes:

Issues Found

ISSUE-01: .intunewin package metadata unreadable by Intune Win32 app wizard

• Discovered: 2026-04-13 during RTVAL-01
• Severity: Blocker — prevents all downstream RTVAL checks (02, 03, 04)
• Symptom: Win32 app creation wizard fields (name, platform, size, MAM enabled) remain empty after file upload; OK button stays greyed out; no portal error shown
• Root cause hypothesis: Detection.xml embedded inside the .intunewin archive is missing, malformed, or uses an unexpected schema version. The IntuneWin32App packager requires a valid detection.xml at the root of the archive alongside the content folder.
• Affected file: Copieur_2eme.intunewin (evidence/Copieur_2eme.intunewin)
• Affected code: ImpTune .intunewin generator (commit 1c3f458)
• Resolution path: Debug the generator to verify Detection.xml is being created, embedded, and follows the expected Intune Win32 app manifest schema. Recommended: run /gsd:debug on the .intunewin generator, OR let phase verification surface this as a gap and use /gsd:plan-phase 10 --gaps to draft a gap-closure plan.
• Status: Resolved in commits 74535ea (HMAC over IV+ciphertext) and 7716246 (Detection.xml alignment with IntuneWinAppUtil.exe reference format). Re-tested 2026-04-13 against live tenant rubis.fr — package now parses; wizard fields populate; OK button enabled.

Sign-off

• All five RTVAL criteria PASS or have documented rationale
• Evidence files committed under evidence/
• Signed by: ___________________