critiquelisted

Critic lenses live as `.claude/agents/critic-<lens>.md` — one isolated agent per lens, each defined by what it reads, said in its `description`; the roster is the scan of those files. Adding a lens means adding an agent file from `templates/critic.md`; this command does not change (who creates a lens, and when: CLAUDE.md, Isolated reviewers). The rules shared by every lens — isolation, the documents-only remit, regression first, calibration, the shape of a finding, the report file and the FND ledger entries — live in the contract skill `.claude/skills/critic-contract/SKILL.md`, preloaded into every lens file through its front-matter, whose own part is its Lens section; nothing of them is restated here (POS.1070, POS.1120). The critic is the mirror of the challenger (`/challenge`): personas there, lenses here, CHL there, FND here, a walkthrough for both. This command only chooses the lens, passes the project and verifies the bookkeeping. **Bare `/critique` — the roster.** List the available lenses (scan `.claude/agents/critic-*.md`) and recommend which fits the project's state — `essence` as soon as a second layer exists, `clarity` before a handover. A recommendation, never a gate. No lens runs at a save; `/release` offers `essence` once (POS.1100); every run is the principal's word. **`/critique <lens> [artefact] [slug]` — run it.** The target is an artefact named as `/forge` names it — `brief`, `brief-<name>`, `intent`, `assignment`, one day `brd` or deeper layers: for `c