rollbacklisted

# Cladding rollback Run `clad rollback <featureId>` from the project root. The verb is the partner of `clad checkpoint` (iron-law.md §2.5 Iron Law backbone Phase 1) — it stamps a `feature_rolled_back` event into `.cladding/events.log.jsonl` and prints the `git checkout <sha>` command the maintainer can run. **Cladding does not run the checkout itself** — the host's branch policy, dirty-working-tree state, or detached-HEAD concerns may demand a non-default strategy, so the decision stays with the maintainer. - `-r, --reason <reason>` — optional free-text reason recorded on the event payload. Useful for post-mortems and the Librarian's archival flow. ``` clad rollback F-001 clad rollback F-a3f9c2 --reason "specialist dispatched a regression on the L1 lint gate" ``` The output is a single Pulse line plus the restoration command: ``` ✓ rollback · F-a3f9c2 target head=<sha12> ts=<iso> Run: git checkout <sha40> ``` When the latest checkpoint has no `gitHead` (the project is not a git repo), the verb prints `No git head pinned — restore spec.yaml manually from VCS history.` instead. ## Exit codes - `0` — rollback event stamped, restoration command printed. - `1` — no prior checkpoint exists for the feature; nothing to roll back to. Run `clad checkpoint <featureId>` next time before mutating. - `2` — feature id argument missing. ## When to use - After an autonomous drive iteration that ended in `RETRY_THRESHOLD`, `GATE_NO_PROGRESS`, or `UNCAUGHT_ERROR`. - After a manual im