karvey-initlisted

# Karvey Init ## Purpose Create a new change and register its Epic in the team's management tool (`../karvey/rules/management-adapters.md`). The first time Karvey is used in a project it also asks the **team settings** — notification channel, task tool and status flow — because a plugin cannot run anything at install time (Step 3.2). `S="${CLAUDE_PLUGIN_ROOT}/scripts/karvey-state.py"` and `C="${CLAUDE_PLUGIN_ROOT}/scripts/karvey-config.py"` below. ## Execution steps ### Step 0 — Settings-only mode (`--settings`) — STOP after it If invoked as `/karvey-init --settings` (or the user only asks to configure the team), run **Step 3.2 only**: pre-fill every question with the current values, merge the answers without dropping untouched keys (`events`, `location`, custom keys), write `project.json` on a docs branch (Step 3.3), print the `Settings:` line and **STOP**. No change-id, no `docs/spec/changes/…`, no `spec.json`, no tracker item. If `project.json` does not exist, say so and ask whether to create a minimal one (Step 3 fields) — nothing else. ### Step 1 — Verify pre-spec context If a `karvey-grill` summary exists in the conversation, use it to pre-populate the fields. If not, ask the user: "Briefly describe the problem this change solves." ### Step 2 — Generate change-id If `$ARGUMENTS` includes the change-id, use it. If not, generate it from the description: - Format: `{add|fix|update|remove}-{descriptive-url-safe-name}` (lowercase letters, digits, hyphens), e.g. `ad