install-loop

# Install Loop Engineering ## Goal Leave the repo with a scaffolded **report-only** loop, a **Loop Ready** score, and clear next actions — using the **single** CLI: ```bash npx @cobusgreyling/loop ``` Do **not** deprecate or remove existing `loop-init` / `loop-audit` usages you find; both doors stay valid. Prefer `loop` for new work. ## Steps 1. **Detect context** - If `LOOP.md` or `STATE.md` already exists, run doctor only (skip init unless human asks to re-scaffold): ```bash npx @cobusgreyling/loop doctor . --json npx @cobusgreyling/loop status . ``` - Otherwise continue. 2. **Pick pattern** (default: `daily-triage`) | Pain | Pattern | |------|---------| | Morning chaos / unclear priorities | `daily-triage` | | PRs stalling | `pr-babysitter` | | CI red / flakes | `ci-sweeper` | | CVE / Dependabot noise | `dependency-sweeper` | | Post-merge TODOs | `post-merge-cleanup` | | Stale release notes | `changelog-drafter` | | Noisy issues | `issue-triage` | 3. **Pick tool** — `grok` | `claude` | `codex` | `opencode` (default `grok`). 4. **Scaffold** ```bash npx @cobusgreyling/loop init . --pattern <pattern> --tool <tool> ``` Optional harness (only if human wants Foundry): add `--with-foundry`. 5. **Doctor** ```bash npx @cobusgreyling/loop doctor . ``` - Exit `0` = healthy · `1` = warnings · `2` = blocked - Follow the **top 3** printed actions; do not invent extra architecture. 6. **Cost chec...