v1.0.21

Added

• Five CLI subcommands that were missing: goto, key, scroll, screenshot, html. The daemon has always
  implemented all of them and the MCP bridge exposes them, but browser-agent could only move, click and type. An
  agent with SSH access and no bridge installed could act on whatever page fetch happened to leave behind and
  nothing else — it could not navigate, press a key, scroll, look at the page, or read it back. The plan listed
  four of the five; goto was the one it missed, and it is the one that matters most, because a session you cannot
  navigate is a session you cannot use.

  A test now reads /action's own action set out of the daemon and the subcommand list out of the parser, and fails
  when they diverge — so the gap cannot reopen silently the way it opened.

  screenshot writes the PNG to a path (a temp file when none is given) and reports its size, and never puts the
  base64 on stdout. html prints the page, or writes it to a file with --out and reports only its length — a
  rendered page is routinely a megabyte.

Fixed

• scroll --x without --y failed in the daemon with a 500 naming a browser. The daemon validates x/y as a
  pair before it starts the browser, so the CLI now raises the same message before sending anything. Failing in the
  CLI gives the caller the real reason instead of a browser-start failure they did not ask for.

Changed

• goto omits use_proxy unless --proxy is given, matching the bridge: sending false would forbid WARP and
  drag a proxied session back to direct, and the daemon treats an absent field and null identically, so omitting
  costs nothing and keeps the payload shape equal to what was actually requested.

• The new action subcommands share the existing "daemon must be running" behaviour rather than fetch's in-process
  fallback, and the reason is now written down: every one of them acts on a live session, so a one-shot session would
  move the mouse in one Chrome and click in another.