Route browser commands to a specific Chrome profile

Add --profile to every socket-using CLI subcommand and to `obu mcp`. The
selector accepts a Chrome profile directory name, the display name from
Local State, or the extension instance UUID (case-insensitive).

Resolution is CLI-side: enumerate sockets, call getInfo on each, and match
metadata.extensionInstanceId against a byte-grep of every profile's
Local Extension Settings/<extension-id>/*.{log,ldb}. The UUID is written
per-profile by the extension's chrome.storage.local and appears verbatim
in LevelDB log bytes, giving a stable instance -> directory mapping
without any host or extension changes.

`obu profiles --connected` joins the on-disk profile list with running
hosts. When no socket matches the requested profile, the error names the
profiles currently connected so the user knows where to look.

Update the skill with a Multi-profile handling section so agents probe
profiles first and lock --profile for the rest of the task.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: 2 people