Fix Windows node auto-update stuck version

On prod (app.jaah.ai › Nodes), the Windows node `win3-auto-deployed` (online, Enabled, last seen 2026-10-26 21:53) reports 1.2.4672 (behind) while 23 Linux nodes moved to 1.2.4746. It skipped at least one release, so the Windows updater is not picking up new versions. - Find why the Windows node does not self-update and fix it so it follows releases like Linux nodes. - The node detail should say why it is behind (last update attempt and its error), not just "(behind)". Out of scope: Linux node updates; the rename waves. Done means: - The node reaches the current prod release without a manual reinstall, and the node detail shows the last update attempt's outcome.

Cause: 1.2.4746 prod deploy's platform-bundle job was cancelled, so no Windows zip existed; node now self-updated to current 1.2.4783. PR #7101 merged (7859c2a8f): updater log now ships (ACL fix), Windows outcomes fold into update history, node detail shows "update failed Xm ago" + cause. Quick gate green; review lanes pass; visual check done. Draft follow-up #10533. Memory: none applied.