Complete hardware-dependent testing before tagging v1.0.0-beta.1

[antonflor]

Follow-up: complete hardware-dependent testing before tagging v1.0.0-beta.1

Type: Task / release gate
Milestone: v1.0.0-beta.1
Context: PR #1 (Launch RecallManager v1 beta) merged to main as 46855bb. Read-only paths were verified live; the change/restore paths and supported-hardware testing were not exercised and remain the gate before any beta tag.

Already done (in PR #1)

• PSScriptAnalyzer: 0 errors (16 intentional warnings — CLI Write-Host, -Profile param name)
• Pester on PowerShell 7: 7/7 passing
• Read-only commands verified on a non-Copilot+ device (build 26200): Status, Audit, Plan, Audit -Format Json
• Fix: read-only $IsWindows assignment in Get-RecallWindowsInfo
• Fix: Pester discovery-phase module load in tests/RecallManager.Tests.ps1

Outstanding — required before tagging beta

Automated

• Pester on Windows PowerShell 5.1 (module targets 5.1+; only PS7 has been run)

Manual test matrix (from docs/testing.md)

• Non-elevated Apply fails with a clear elevation message
• Plan -Profile SnapshotsOff — no writes; lists backup, policies, verification
• Apply -Preview — native WhatIf output; no registry or feature changes
• Apply -Profile SnapshotsOff — policies written, component unchanged, audit reports SnapshotsBlocked/Disabled
• Apply -Profile PrivacyHardened — policies written, feature disabled/removed, restart surfaced
• Restore — restores policy values from the latest backup

Requires an eligible Copilot+ PC

• Validate all four profiles end-to-end (AuditOnly, UserControlled, SnapshotsOff, PrivacyHardened)
• Validate restore after each change profile
• Confirm pending-restart reporting (DISM 3010 path)

High-risk checks (from docs/testing.md)

• Confirm SnapshotsOff behavior against current Microsoft docs + installed build
• Confirm whether existing snapshots are deleted by policy on the test device
• Confirm feature removal + restoration with and without network access
• Confirm domain/MDM policy does not immediately overwrite local values
• Inspect backup permissions under %ProgramData%\RecallManager\Backups

Docs / release

• Capture and redact real screenshots; replace the SVG placeholders in docs/images/
• Review README and profile copy against observed behavior
• Tag v1.0.0-beta.1 only after supported-device testing and restore testing pass

Notes

• Do not publish a stable v1.0.0 tag until supported-device + restore testing are complete.
• Test device used so far: TM-Z13, build 26200 (25H2), Recall reported Unavailable (not Copilot+ hardware), so change paths could not be meaningfully exercised there.