v2.5.85 - Resume saved-user updates automatically

User-only updates now stay queued after headless servicing finishes. Sign in as the saved user and the cycle resumes automatically. No manual rerun required.

• Stops the SYSTEM fallback once only saved-user work remains. An already signed-in saved user gets an automatic retry too.
• Fixes a launcher race that could overwrite the record of a completed legacy upgrade.
• Gives delayed-start Windows Time a bounded chance to start before reporting an early health failure. The health check still does not start or reconfigure services.
• Corrects deployment messages about which account runs updates and when user updates resume.

Validation: 645 tests passed, along with the User/SYSTEM exclusion and published launcher upgrade gates. Windows 11 VM rows A, G and N passed, including killed-process recovery and protection against duplicate runs. Automatic saved-user sign-in resumed the cycle and cleaned up tasks, state and temporary autologon settings.

Known limitation: VM B remains PARTIAL because Windows Update offered KB5007651 again after successful installation. It is reported as deferred inventory, not counted as a completed update. Follow-up: #96.

The VM matrix did not cover Windows 10, RDP, simultaneous interactive sessions or real upgrades of user-installed apps. Detailed evidence and coverage limits: https://github.com/nanoDBA/boot-upd/blob/master/docs/validation-user-continuation.md. These VM runs tested the implementation before the release-only version bump.

Published-asset verification: all ten SHA256 sidecars and expected line endings passed. The exact README bootstrap passed on hosted Windows VMs from Windows PowerShell 5.1 for both fresh installation and legacy repair: https://github.com/nanoDBA/boot-upd/actions/runs/40154970065.