dashboard-secretlisted

## Why this exists Some credentials can only be obtained by clicking around a web dashboard — there is no `gcloud`/`supabase`/API call that returns them. Never ask the user to paste the raw secret into chat — it stays in the transcript. The default is: the user clicks reveal/reset/copy themselves, in their own browser session. That default exists mainly to stop the plaintext value from ever landing in something that persists it where a later reader (human or model) could see it — most concretely, a `computer` screenshot taken to verify a browser click, which would capture live secret text as an image in the tool-call history. **Narrow exception — I (Claude, via Chrome MCP) may do the click myself** when the user explicitly asks for it for a specific credential, AND the leak vector above is actually avoided: - Click the **copy-to-clipboard icon only**. Never click "reveal"/the eye toggle first — the copy icon grabs the real underlying value regardless of whether it's currently masked on screen, so there's no need to display it. - Take **no screenshot** of that page between locating the copy control and clicking it, and none after. Use `find` (semantic element lookup, returns refs/descriptions, not rendered content) to locate the control instead of `computer screenshot`. - If the copy icon can't be found/clicked without a reveal step in the way, stop and fall back to asking the user to click it themselves — don't reveal-then-screenshot to "verify" the click wo