v2.5.82 - Native SSMS updates and reboot verification

Running upd.cmd now invokes native servicing for existing SSMS 22 installations through Visual Studio Installer, using each instance's configured update channel. Fresh inventory must verify the target build; busy installers, open SSMS, and unavailable metadata remain retryable. Reboot evidence and update accounting survive checkpoints.

Use upd --skip-ssms (PowerShell: -SkipSsms) to skip native SSMS servicing. The choice survives deployment, self-update, and reboot resume, including explicit false values. Winget and Chocolatey retain their existing package selection.

Final Windows Update scans now receive a fresh settled reboot check before completion. The VM collector also requires active-state cleanup before reporting completion.

Validation:

• 577 local tests passed; user/SYSTEM exclusion and published-launcher upgrade gates passed.
• All 43 PowerShell files parsed with no error-severity analyzer findings; GitHub CI passed.
• Native SSMS VM upgrade: 22.9.2 to 22.10.1, followed by a verified no-op.
• Default upd.cmd VM: PASS, three independently confirmed reboots, native SSMS phase executed, and no remaining tasks, active state, or CBS reboot marker.
• Headless -SkipSsms VM: skip/resume/cleanup verified across two OS-confirmed reboots. Overall PARTIAL because user-scoped work and the KB5007651 re-offer remained explicitly deferred.

The native installer did not request a reboot during its upgrade; native 3010/1641 recovery has regression coverage but was not exercised by that live install.

Detailed validation. Issues: #73, #74, #75.