v1.0.10

Added

• use_proxy on browser_action. The daemon has honoured the field on /action
  for its whole life, but it was in neither the zod schema nor the advertised
  inputSchema, so an agent could only say "all fetches via WARP" and never "this one
  goto via WARP". It is now a real boolean on both surfaces, forwarded verbatim.

  The description carries the two consequences that are otherwise silent, because an
  agent that learns them from a failed turn has already wasted one: switching the route
  restarts Chrome and drops cookies and page state, so it belongs once per session
  rather than per click; and goto returns {ok, url, title} with no blocked field,
  so a forced route that degraded to direct looks like a success.

Changed

• browser_action now omits use_proxy instead of sending false. false
  forbids WARP and drags a proxied session back to direct; omitting it leaves the
  session on the route it is on. browser_fetch still sends null on purpose, because
  there null is what enables the daemon's auto-retry — the two tools want different
  defaults for the same field, and a test pins each.