drakezhangandCursor 31d2a1b3dc Gate liveness reaping on heartbeat capability ...

Only reap browsers that have sent at least one `system.heartbeat`.
A pre-heartbeat extension never opts in, so it is never dropped on
silence and keeps relying on socket-close detection exactly as before.
This removes a backward-compat regression where a new daemon paired
with an old extension would wrongly reap a live-but-idle connection
and then report `no_browser_connected` on the next command.

- Add a `heartbeat_seen` flag to `BrowserClient`, set when a heartbeat
  event arrives, and exclude never-heartbeated clients from
  `stale_browsers`.
- Cover both the opt-in and the legacy-survivor cases in unit tests.

Co-authored-by: Cursor <cursoragent@cursor.com>

2026-07-22 13:06:17 +08:00

..

bsk-cli

Gate liveness reaping on heartbeat capability

2026-07-22 13:06:17 +08:00

bsk-protocol

Lock system.heartbeat wire name with a contract test

2026-07-22 12:30:46 +08:00