[Angnuo (angnuoli)]

Description

Approving the bundled Windows node currently forces a full host-process restart even though the pinned client can reconnect after node.pair.resolved. Prefer that reconnection, retaining the existing restart path when it cannot be confirmed within five seconds.

Restore the installer's previous Defender exclusions, elevation handling and marker format, including the matching reset-script scope.

Related Issue

None.

Changes

• Confirm reconnection through an observed disconnect/reconnect or an increased connectedAtMs; retain process-identity and command-surface checks.
• Keep the required restart after initial device pairing, and record same-process versus restart-fallback timing for node authorization.
• Update regression cases for reconnection, stale connections, cancellation and unexpected commands.
• Document the observed first-open baseline separately from the unmeasured optimization.

Type of Change

• Bug fix
• Documentation update

Testing

• Local tests and builds were not run, as requested by the user.
• Regression cases were updated but have not been executed locally.
• The documented 43.907-second service-ready baseline predates this change; no speedup is claimed for the new implementation.

Checklist

• Reviewed the diff and kept the PR limited to the intended changes.
• Updated the corresponding documentation and regression cases.
• Tests pass locally.
• Build succeeds locally.
• Manual validation of the new startup path is complete.