dashboard-forge
dashboard-forge — supervised dashboard automation doctrine
Some operations exist ONLY behind a vendor's web UI (GitHub fine-grained PATs and OAuth apps have no creation API; a Cloudflare token cannot grant itself new scopes). This skill is the canonical method for automating those click-paths safely: the human supervises and handles logins/2FA; the scripts do everything else, reproducibly.
Harness (SSoT): this plugin, in two forms on shared foundations (plugin CLAUDE.md has the file map):
- Recipes —
scripts/web-forge.ts(Bun): the step-and-shoot method as a CLI. A recipe is data (flags or a--specJSON file → form operations), with idempotent ensure, read-back from a fresh load, a screenshot per step, a login gate that never types a credential, andDriver.extractToVaultfor reveals. Write new console automation as a recipe. Worked family: admin-console (Google Admin).bun "$(cc-plugin-root web-forge)/scripts/web-forge.ts" recipes --jsonlists every recipe, flag and exit code. - Forge scripts —
lib/browser-forge.mjs(node ONLY: Bun'sconnectOverCDPtimes out; needsplaywright-core, pinned at the repo root): Playwright held directly over CDP, for flows a recipe does not cover yet — token capture off the wire (captureBearer), consent dismissal, exact-name clicks. The cf-access-wall and azure-provision scripts use it.
Both take their browser from lib/forge-chrome.mjs and their secret sink from lib/vault.mjs.
Route choice — the two connection modes. If the session you need is already signed in to a profile of your everyday Chrome, use extension mode (recipes: --connect extension, the default): chrome-profiles (chrome-profile.sh setup <email>, zero clicks). For a supervised flow that wants its own isolated, persistent profile, use cdp mode (recipes: --connect cdp --site <name>; forge scripts: launchChrome(site)). Route ladder and Chrome-136 mechanics: chrome-profiles is the SSoT.
Self-Evolving Skill: dashboards drift constantly. When a selector misses or a flow changes, fix the recipe or forge script AND append the drift note to the Vendor Quirks section below — immediately, not later. Only update for real, reproducible breakage.
The method — step-and-shoot
Write the forge as small, resumable steps against a LONG-LIVED Chrome (launch once; each step connects, acts, disconnects — browser.close() on a CDP connection only detaches, Chrome keeps running). Never author one monolithic script against an unseen UI.