pi-chrome 0.13.0: flatten /chrome tree, cycle-on-pick for clicks/quiet, status header

Reorganises the /chrome command surface:

  /chrome status   - one-line snapshot of connection + click mode + quiet mode
  /chrome doctor   - full health check (unchanged)
  /chrome onboard  - install extension (unchanged)
  /chrome clicks   - cycles auto -> on -> off -> auto when called with no args.
                     Explicit args (auto|off|on|status) still work.
  /chrome quiet    - toggles on/off when called with no args.
                     Explicit args (on|off|toggle|status) still work.

Removes the nested 'settings' wrapper. /chrome settings background/trusted
still functions as a hidden legacy alias but is no longer advertised.

Bare /chrome opens a picker with a one-line status header and cycle-target
labels: 'clicks: auto -> switch to on' / 'quiet: off -> switch to on'. No
second picker; one keypress flips the setting.

Argument autocomplete now returns full-path values (e.g. 'clicks auto') so
pi-tui's whole-argument replacement applies correctly. Top-level suggestions
show clicks / quiet / status / doctor / onboard with descriptions.

User-visible names match the descriptive copy:
  - 'trusted' -> 'clicks' (matches 'real-looking clicks' / 'quiet clicks')
  - 'background' -> 'quiet' (matches 'quiet mode' / 'watch mode')

README + agent prompt primer + internal hint strings updated.

1 files changed, 9 insertions, 9 deletions

diff --git a/README.md b/README.md
index 5a09082..0387dce 100644
--- a/README.md
+++ b/README.md
@@ -11,7 +11,7 @@ Multiple Pi sessions can use Chrome at the same time. The first Pi session start
 ## Why try it?
 
 - **Uses your existing Chrome profile** — works with the Chrome windows/tabs you are already using, including logged-in GitHub, admin dashboards, local apps, and internal tools.
-- **Watch your authenticated Chrome work** — by default, `chrome_*` tool calls focus Chrome and activate the target tab so you can see the agent inspect, navigate, click, and type in real time. Switch to silent/background mode for the whole session with `/chrome settings background`, or pass `background: true` on a single tool call when you want quiet.
+- **Watch your authenticated Chrome work** — by default, `chrome_*` tool calls focus Chrome and activate the target tab so you can see the agent inspect, navigate, click, and type in real time. Switch to silent/background mode for the whole session with `/chrome quiet`, or pass `background: true` on a single tool call when you want quiet.
 - **Full browser automation toolkit for Pi** — list/create/activate/close tabs, snapshot pages with usable CSS selectors, navigate, evaluate JavaScript, click, type, press keys, wait for page state, and capture screenshots.
 - **Built-in setup and agent guidance** — `/chrome onboard` walks users through installing the companion extension, `/chrome doctor` checks connectivity and version drift, screenshots save to disk, and the prompt primer tells agents to inspect with `chrome_snapshot` before acting and avoid destructive actions unless explicitly requested.
 
@@ -72,13 +72,13 @@ pi-chrome can drive Chrome two ways:
 - **Quiet clicks** — fast and unobtrusive. They work on most sites, but some pages (sign-in flows, copy-to-clipboard buttons, file pickers, autoplay videos, fullscreen, paywalls) ignore them because they don't look like a real human action.
 - **Real-looking clicks** — indistinguishable from a person clicking. They unlock the cases above, but Chrome shows a *"Pi Chrome Connector started debugging this browser"* banner at the top of every tab pi-chrome touches while it's working.
 
-Pick a mode with `/chrome settings trusted`:
+Pick a mode with `/chrome clicks`:
 
 ```text
-/chrome settings trusted auto     # default; quiet by default, real-looking only when needed
-/chrome settings trusted off      # always quiet, no banner ever
-/chrome settings trusted on       # always real-looking, banner stays up the whole session
-/chrome settings trusted status   # show the current mode
+/chrome clicks auto     # default; quiet by default, real-looking only when needed
+/chrome clicks off      # always quiet, no banner ever
+/chrome clicks on       # always real-looking, banner stays up the whole session
+/chrome clicks status   # show the current mode
 ```
 
 For a one-off call, pass `trusted: true` (or `false`) on `chrome_click`, `chrome_type`, `chrome_fill`, `chrome_key`, `chrome_hover`, `chrome_drag`, or `chrome_scroll`. The per-call value wins over the global mode.
@@ -92,9 +92,9 @@ By default, `chrome_*` tools focus Chrome and activate the target tab so you can
 When you want quiet (planner / audit / worker sessions running alongside your editor), turn background mode on for the whole Pi session:
 
 ```text
-/chrome settings background          # toggle
-/chrome settings background on       # explicit
-/chrome settings background off      # explicit
+/chrome quiet          # toggle
+/chrome quiet on       # explicit
+/chrome quiet off      # explicit
 ```
 
 For a single tool call, the agent can pass `background: true` directly. The per-call value always wins over the session toggle.