qualitylisted

Assess the quality of the **current working directory's repo** against Rhiza standards. This is the global variant of the per-repo `rhiza_quality` command synced from `jebel-quant/rhiza`; it adapts to whichever repo it runs in by reading that repo's `CLAUDE.md`, `.rhiza/template.lock`, and git remote at runtime. ## 0. Establish the mode — how much of this repo is Rhiza's These three checks come **first — before any `make`, any tool, any analysis**, because they decide which half of this command applies: ```bash test -f .rhiza/template.yml # rhiza-managed at all? test -f .rhiza/template.lock # ...and actually synced? test -f .rhiza/template-bundles.yml # ...or is this repo the template itself? ``` | `template.yml` + `template.lock` | **Full mode** — the template's gates plus the design assessment. | | `template.yml` only | **Degraded mode** — managed but never synced, the state `/init` deliberately leaves behind. Mention `/rhiza:update` performs the first sync, then continue. | | `template-bundles.yml`, no `template.yml` | **Template mode** — this repo *is* the template. See below; **never** suggest `/rhiza:init` or `/rhiza:update` here. | | None of them | **Degraded mode** — not rhiza-managed. Mention `/rhiza:init` once, as information, then continue. | **The pointer wins where both appear.** `template-bundles.yml` is decisive only when there is no `template.yml`: a repo with a pointer is a *consumer*, whatever else its `.rhiza/` holds. **The sec