configlisted

# config — change PACT settings See [`workflow-map.md`](../../references/workflow-map.md). Read-only inspection does not gate on schema; any write does (`pact schema --gate`). ## Modes ### `show` Print the current `config.toml` and `stack.toml` values grouped by section, plus the constitution version and which `[steps]` are on. ### `statusline install` The main status line must live in user or project `settings.json` (a plugin cannot set it). Ask: user-level (`~/.claude/settings.json`) or project-level (`.claude/settings.json`). Add: ```json "statusLine": { "type": "command", "command": "<abs path>/scripts/statusline.sh" } ``` Refuse to overwrite an existing `statusLine` unless the user passes / confirms `--force`. Back the file up first. The script always renders a colored base segment (model, folder, full path, context-window usage, total tokens), then adds a colored PACT segment (flow mode, project, spec/story progress) only inside a PACT project — a user-level install stays a sane baseline everywhere. ### `project expand` Turn `.pact/project.md` into a fuller PRD under `docs/` and, optionally, create `status: draft` spec stubs — one per capability the brief implies, with `depends_on` where an ordering is implied. The user activates them one at a time with `pact spec <slug>`. ### free text ("turn on review", "switch to squash merges", "notify me on failures") 1. Identify the target key(s) in `config.toml` / `stack.toml` / the constitution. 2. Show the current v