cleanup

Context

• Repository: !git remote get-url origin
• Current branch: !git branch --show-current
• Feature store: each feature lives in .feature-dev/features/<slug>/, managed by ${CLAUDE_PLUGIN_ROOT}/scripts/features.py (pass --root <repo root>). Layout: artifact-locations.md.

Phase 0: Discover Features

Run ${CLAUDE_PLUGIN_ROOT}/scripts/features.py list --json --root <repo root>. Each entry has slug, status (draft, approved, planned, running, halted, implemented, invalid), plan (steps, completed, halted_at, halt_reason, or null), issue (a ref or null), artifacts (kind, path, needs_review) and, for an invalid feature, a reason. A missing .feature-dev/features/ is an empty list.

The review history, review files and server pointer of a feature live inside its folder, so one feature is one unit: nothing is matched by slug prefix, and no review data outlives its feature.

If the list is empty, STOP and tell the user: "No features found. Nothing to clean up." Do not proceed.

Phase 1: Categorize

Build three lists from the status of each entry.

Safe to delete:

• Features with status implemented — the work is done. The features.py delete command itself removes only these, so this list and the script agree.

Active work (never offer for deletion):

• Status running or halted — a /feature-dev:tdd run is mid-flight or resumable. Deleting one discards its plan.completed record and strands a dirty working tree with no way to tell which steps already landed.
• Status draft, approved or planned — work in progress.

Ambiguous (do not offer by default — the user can delete manually):

• Status invalid — a broken feature folder; surface its reason, never include it.

Phase 1a: Stale review-server pointers

While a review page is served, .feature-dev/features/<slug>/reviews/.url holds its address. For every feature that has one, other than a running or halted feature, Read it and probe <url>alive (the pointer ends in /): curl -s -o /dev/null --max-time 2 <url>alive. /alive answers without a token and without resetting the server's idle timer, so the probe never keeps a forgotten review open. Exit 7 (connection refused) means no server — the pointer is stale. Any other exit means something answers — a review in progress:

• move the feature from Safe to delete to Active work with reason review in progress — the review's verdict is about to be applied to it;
• say "review server running at — submit or close it, then rerun".