0.17.2: fix /next lastSeenAt + strict daemon version match

Bugs surfaced in real-world 0.17.0/0.17.1 testing:

1. Daemon /next only recorded lastSeenAt AFTER the auth/pair checks. Pre-pair
   the daemon returns needsPairing early without recording the poll, so
   connected stayed false even though the extension was polling. /chrome
   onboard's wait-for-poll loop spun forever on a healthy extension.

   Fix: record lastSeenAt at the top of /next for any chrome-extension
   origin, before auth checks. Onboard now correctly detects 'extension
   alive but unpaired' which is the precise state during pair step.

2. Daemon compatibility was checked at major.minor match. Result: a patch
   release fixing a daemon bug (like #1) couldn't replace the running
   daemon — new Pi client joins old buggy daemon as client.

   Fix: exact version match. Patch releases auto-kill+respawn the daemon.

0 files changed, 0 insertions, 0 deletions