docs(validation): record that the agent is never sent to a Windows 11 Home device

[fadwen]

Summary

The "Windows on ARM" section of Validation/Findings.md was a host survey with the agent's own behaviour marked pending. The one ARM64 device available runs Windows 11 Home, so on 16 October it was Entra registered and MDM enrolled in the dev tenant, placed in a device group of its own, and 27 existing experiments were assigned to that group, to find out whether the Intune Management Extension arrives on Home at all and, if it did, what it does on ARM64.

It does not arrive. In 75 minutes and 11 syncs the service addressed DMClient, NodeCache, Policy/ConfigOperations/ADMXInstall and LAPS, and never EnterpriseDesktopAppManagement, the CSP that delivers the agent's MSI. No agent folder, service, log or registry key; no run state for any of the 27 policies; no row for the device in the Win32 apps' install report. That matches the documentation's "excluding Windows Home", and the ARM64 agent behaviour stays pending until a Pro or Enterprise ARM64 device is enrolled.

A second observation came for free: the tenant's LAPS policy, assigned to All devices, reached the device on its first four syncs and failed on every node with 0x86000011, the CSP's "not supported on this edition" result, as the LAPS CSP's edition list says.

Changes

• Validation/Findings.md: the ARM section's pending note says why it is still pending; a new "Windows 11 Home: the agent is never sent" subsection records the enrollment, the two observations with their evidence, and that nothing changes for the tool.
• CHANGELOG.md: Changed entry under Unreleased.

Verification

• Evidence read from the device's DeviceManagement-Enterprise-Diagnostics-Provider/Admin log (44 events, 03:51 to 04:54 UTC), the agent's install paths and registry keys, Intune's managedDevices record (skuFamily = Home), the policies' deviceRunStates, and a DeviceInstallStatusByApp export job. Nothing on the device was changed beyond the enrollment; the tenant changes (a group, a user, a LAPS exclusion, the 27 extra assignments) are being removed.
• Markdown only; no code or help changed.

[fadwen]

Notes on the lines whose reason the diff does not show.

[fadwen]

Filed under the ARM section rather than as a round of its own because the device was enrolled for the ARM question; the Home result is what stopped that question being answered, and a reader looking for ARM evidence should find out here why there is none yet. The 75-minute window is longer than every assignment-propagation figure the README records (2 to 8 minutes, Win32 by push in seconds), which is what makes eleven syncs with no EnterpriseDesktopAppManagement command a result rather than a wait.

[fadwen]

Stated explicitly because it is the only Findings entry whose observed behaviour has no rule behind it: the module analyzes scripts for where the agent runs them, and a device the agent never reaches is outside that. Get-IslHostArchitecture is named so the reader knows the ARM64 code paths still rest on the host survey above, not on an agent run.