/**
 * studiograph settings — CLI for the non-secret half of the encrypted store.
 *
 *   studiograph settings list                    Inventory of stored settings + values
 *   studiograph settings get <key>               One value
 *   studiograph settings set <key> <value>       Write or replace a setting
 *   studiograph settings delete <key>            Clear (reverts to registry default)
 *   studiograph settings schema                  Show every registered key, default, and constraint
 *
 * Targets registry workspace-setting keys (model.provider, model.id,
 * r2.account_id, r2.bucket, r2.public_url, search.provider,
 * search.google.cx, …) — the same surface the Web Providers panel
 * writes via `PUT /api/settings/:key`. Secrets go through
 * `studiograph secrets`; this command refuses non-setting classifications.
 *
 * Mirrors the shape of `studiograph secrets` (list/get/set/delete) so
 * operators already familiar with that command don't have to relearn
 * anything. Values are JSON-serialized in the store; for enum/string
 * settings the value is what you'd type at the prompt. Numeric and
 * boolean values are accepted as their plain typed form (`true`,
 * `false`, `42`) — set converts to a JSON value before storage.
 *
 * Authentication: same model as `studiograph secrets` — the master key
 * is the gate. If you can read `~/.studiograph/master-key`, you can
 * read/write the store.
 */
import { Command } from 'commander';
export declare const settingsCommand: Command;
