@dropthis/cli 0.35.0 → 0.37.0

package/README.md

@@ -199,9 +199,10 @@ These flags are inherited by all commands:
 |------|-------------|
 | `--api-key <key>` | Override API key for this invocation |
 | `--api-url <url>` | Override API base URL |
-| `--json` | Force JSON output |
+| `--json` | Force JSON output (implies non-interactive — never prompts) |
 | `-q, --quiet` | Suppress status output and imply JSON |
 | `--no-interactive` | Disable interactive prompts (inline auth, confirmations) |
+| `--insecure-store` | Store credentials in a plaintext file instead of the OS keyring, for headless/CI boxes without a keyring backend (also `DROPTHIS_INSECURE_STORE=1`) |
 
 ## Update
 
@@ -355,6 +356,7 @@ The CLI is designed for non-interactive use. In non-TTY environments (pipes, CI,
 export DROPTHIS_API_KEY=sk_live_...    # API key (same as --api-key)
 export DROPTHIS_API_URL=https://...    # Override API base URL (same as --api-url)
 export DROPTHIS_NON_INTERACTIVE=1      # Disable interactive prompts (same as --no-interactive)
+export DROPTHIS_INSECURE_STORE=1       # Plaintext credential file instead of the OS keyring (same as --insecure-store)
 export DROPTHIS_NO_UPDATE_NOTIFIER=1   # Disable the startup update notice (also auto-disabled in CI, non-TTY, --json/--quiet)
 export NO_COLOR=1                      # Disable ANSI color in human output (also auto-disabled when not a TTY)
 ```
@@ -384,7 +386,7 @@ dropthis publish ./dist --url
 | 6 | Domain verification pending (`domains verify` one-shot, not live yet) |
 | 7 | Domain verification timeout (`domains verify --wait` exceeded `--timeout`) |
 
-This table — plus the global flags (`--api-key`, `--api-url`, `--json`, `--quiet`, `--no-interactive`) — is machine-readable from `dropthis commands --json` (the `exit_codes` and `global_options` fields), so an agent can discover the whole surface without scraping docs.
+This table — plus the global flags (`--api-key`, `--api-url`, `--json`, `--quiet`, `--no-interactive`, `--insecure-store`) — is machine-readable from `dropthis commands --json` (the `exit_codes` and `global_options` fields), so an agent can discover the whole surface without scraping docs.
 
 Some failures share exit 1 but carry a distinct error `code` in the JSON envelope:
 
@@ -413,10 +415,10 @@ Run diagnostics to verify CLI health:
 dropthis doctor
 ```
 
-Reports CLI version, auth source (`env`, `flag`, `storage`, or `missing`), and credential storage backend (`secure`, `insecure`, or `none`).
+Reports CLI version, the bundled `@dropthis/node` SDK version, auth source (`env`, `flag`, `storage`, or `missing`), credential storage backend (`secure`, `insecure`, or `none`), and — for a stored key — its capability scopes.
 
 ```json
-{"ok":true,"version":"0.32.0","auth":{"source":"env"},"storage":{"backend":"secure"}}
+{"ok":true,"version":"0.36.0","sdk_version":"0.32.0","auth":{"source":"storage"},"storage":{"backend":"secure"},"scopes":["team"]}
 ```
 
 Add `--online` for a network preflight an agent can run **before** a publish to tell apart the common failures — re-auth vs network vs an unresolved workspace: