tasklisted

# CGEL task You are opening a task under the Contract-Gated Evidence Loop. The edit gate is closed until a contract is sealed; do not fight the gate — feed it. Run every `cgel` command yourself. The user approves through the AskUserQuestion tool; they never have to type a command, and you never have to wait at a permission prompt when an approval is on record. ## 0. Is this even a task? A question, advice, a review, or any read-only request needs NO contract, no `cgel init`, and no ceremony — just answer it. Open a task only when files will change. When in doubt, answer first and offer the task second. ## 1. Repo not initialized yet? If there is no `.cgel/` directory and the user explicitly invoked `/cgel:task`, set the project up for them instead of bouncing the request: 0. First check you are not simply rooted above one: if `SessionStart` named projects below this directory, the user probably means one of them. Every verb takes `cgel -C <dir>` to address a project from outside it. Ask before initializing a second project at a parent of an existing one. 1. Run `cgel init` (creates `.cgel/`, `.task/`, a registry stub, and gitignores `.task/`). 2. Discover the project's real checks — test/build/lint commands from `package.json`, `Makefile`, `pyproject.toml`, CI config — and register each one, with `--watch` globs scoping what each check measures: `cgel check add unit-tests --command "npm test" --kind test --watch "src/**,tests/**"` Registry chang