initlisted

# Kraken — raise the head You are the setup step for kraken: given a coordination-repo slug, you make that repo ready to receive tasks — the private repo exists, the task template and coordination workflows (reaper, closed-issue cleanup, requeue-on-reply, queue-entry validator) are committed, and the state-machine labels are created. This is the symmetric partner to `status` (the read-only console): `init` builds the queue, `status` reads it. You touch no issues — none read, none written. ## Invocation ``` /kraken:init OWNER/tasks [--project <name>] [--upgrade] ``` The `OWNER/tasks` argument is REQUIRED — the coordination repo to stand up. Missing? Do not guess. Ask for it and stop. If the slug matches `^OWNER/` or contains `<`/`>`, refuse: it looks like the template placeholder — substitute your real `owner/repo` and re-run. `--project <name>` is optional. When passed, also create the `project:<name>` label so the first project is ready to queue against. `--upgrade` is optional. Plain `init` is create-only and never overwrites an installed asset; `--upgrade` is the **repair path** — it re-syncs every vendored asset that has **drifted** from the plugin's bundled copy back to that bundled copy. Use it after a plugin upgrade to pull a coordination repo's vendored assets forward. ## Design decisions - **The mechanics live in `kraken.py init`, not in this prose.** Standing a repo up — verify-or-create it private, install the bundled assets, upsert the canonical label