configurelisted

# /forged:configure Author the cognitive configuration Forged freezes into new work: which roles exist per assurance profile, and which provider/model answers each role. All edits target the operator authoring config; compiled snapshots in `state.db` are runtime truth, so a config change affects only work started after it. Changing the roster of already-running work is a typed lifecycle operation (`epic revise-roster` / `run revise-roster`) owned by `../manage-work/SKILL.md`, never a config edit. ## Boundaries - The authoring config is `$ANVIL_HOME/config.yaml` (default `~/.anvil/config.yaml`; `FORGED_CONFIG` overrides; `.json` is accepted). - This skill edits profiles, rosters, defaults, and pricing in that file only. It never touches `state.db`, target repositories, provider credentials, or the service manifest. - `forged definition validate` is the acceptance gate; an edit is not done until it passes. - Provider CLIs own routing and authentication. Pointing a provider at an inference gateway happens in that provider's own configuration, not here. - Never invent a price. A model without a rate-card entry reports unknown cost, which is correct until the operator supplies real rates. ## Inspect before editing ```bash export ANVIL_HOME="${ANVIL_HOME:-$HOME/.anvil}" if [ -n "${FORGED_CONFIG:-}" ]; then CONFIG="$FORGED_CONFIG" else CONFIG="$ANVIL_HOME/config.yaml" test -f "$CONFIG" || CONFIG="$ANVIL_HOME/config.json" fi cat "$CONFIG" forged definition vali