runlisted

# Cladding run (formerly `drive`) Run `clad run` from the project root. The autonomous loop: 1. Pre-flight `adapter.healthCheck()` — fails fast on missing credentials or unreachable host. 2. For each ready feature (status `planned`, `depends_on` satisfied): - Specialist dispatch authors the implementation. - Apply mutations to the working tree. - L1 gates: Type / Lint / Arch. - Reviewer dispatch — `HUMAN_REQUIRED` halt if reviewer identity equals specialist (anti-self-cert barrier). - UAT requires a human-pass evidence entry; missing → `HUMAN_REQUIRED` halt. 3. Halt class is one of the 13 enumerated reasons (`ALL_FEATURES_DONE`, `MAX_ITERATIONS`, `WALL_CLOCK`, `BUDGET_EXCEEDED`, `BLOCKED_FEATURE`, `RETRY_THRESHOLD`, `GATE_NO_PROGRESS`, `HUMAN_REQUIRED`, `TRANSPORT_AUTH_FAILED`, `TRANSPORT_RATE_LIMITED`, `TRANSPORT_NETWORK`, `LLM_UNAVAILABLE`, `UNCAUGHT_ERROR`). Budget flags: `--max-iterations`, `--max-wall-clock-ms`, `--max-retries`. `--cwd <path>` targets a project directory other than the current one. `--json` emits the raw Iron Core result; default is the plain Soft Shell summary. ``` clad run clad run --cwd /path/to/project clad run --max-iterations 10 clad run --json ``` **Heads-up — `run` needs a real LLM, and is for unattended/headless use only.** The host AI (Claude Code, Cursor, …) drives work *naturally in-session*; `clad run` is the entry point for the **opposite** case — autonomous, no-human-in-the-loop progress (CI/cron/SDK). Two requirements: