v2.16.15

[2.16.15] — 2026-09-27

Added

• Org runs record the idle watchdog's state when they stop. The org stopped event in bus.jsonl now carries data.idleWatchdog: idle_minutes, when the next idle nudge was due (next_nudge_at), when the run would have been idle-stopped, and any hold in force. idle-watchdog.json (read by org status --json) also gains next_nudge_at. Before this, a run that was cut short, for example a drill bounded by timeout, deleted the watchdog file on stop, and its bus did not show whether a nudge had been missed or simply was not due yet. The default nudge comes after 10 idle minutes. The 5-minute interval is block_recheck_minutes, which applies only to tasks blocked with org_task_block. (#352)

Fixed

• Two browse open launches racing for the same CDP port no longer end up sharing one Chrome. Both launches could see the port as free and start Chrome on it. If the losing launch's Chrome was still starting when the winner's began answering, the loser took the winner's browser as its own and returned the same port. It then recorded its own Chrome's pid, which was about to exit, under that port. Both callers then drove one browser, and the winner's Chrome was left running with nothing able to close it. On a fixed port, a launch now accepts an endpoint only when it reports the browser id that its own Chrome printed on stderr (DevTools listening on ws://…/devtools/browser/<id>). If another Chrome holds the port, the launch waits for its own Chrome to lose the bind and moves on to the next port. Each launch now gets its own profile directory, even when two launches run in the same process. A launch that gives up now kills the Chrome it started, on a fixed port as well as on port 0. Bumped @monoes/monobrowse to 1.0.26.

npm: monomind@2.16.15, @monoes/monomindcli@2.16.15, @monoes/monobrowse@1.0.26 published to the npm registry.