ops-credentials

# OPS ► CREDENTIALS Load `ops-rules` before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If `AskUserQuestion` / `Workflow` are missing, follow Rule 10 in `ops-rules` (Hermes: numbered options / two-turn Telegram card; `delegate_task`). ## CLI/API Reference | Command | Output | | -------------------------------------- | ---------------------------------------------- | | `bin/ops-credentials` | Human table — configured + missing per service | | `bin/ops-credentials --json` | JSON array, one entry per credential | | `bin/ops-credentials --service stripe` | Filter to one integration | The bin script is the source of truth. It scans these sources in order and reports the FIRST hit per credential: 1. Shell env (`$STRIPE_SECRET_KEY`, etc.) 2. `$OPS_DATA_DIR/preferences.json` (`.revenue.stripe.secret_key`, etc., including `doppler:KEY` references that get resolved live) 3. macOS Keychain (`security find-generic-password -s <name> -w`) 4. Dashlane (`dcli password <keyword> --output json`) Values shorter than 12 chars print as `•••`; longer values print as `first6•••last4`. ## Your task When the user runs `/ops:credentials`: 1. **Run** `bin/ops-credentials` and present the output verbatim — it's already formatted for the user's terminal (compact mode for SSH/mobile, table layout otherwise). 2. **Offer follow...