cleanlisted

# Disk hygiene Audit first; mutate only after a fresh deterministic preview and explicit approval of one tier. A filename pattern is a discovery hint, never proof that an entry is junk. Read [the safety model](reference/safety-model.md) before the optional execution lane. ## Arguments and boundaries Parse `$ARGUMENTS` as optional `--execute`, optional `--policy <file>`, and one target directory. `--execute` means "deletion may be offered" on every platform — the gated engine lane where the platform supports it, the manual handoff elsewhere; it is not approval. (Deliberate semantic unification, not a restatement: the flag previously read as engine-lane-only, which left the manual lane's gate ambiguous — consumer sessions read it both ways.) With no target, ask once. Reject an OS-managed root, a non-root mount target, a protected shell-folder root or descendant, a missing directory, a symlink, or a Windows reparse point. A whole-volume root that is not OS-managed (a Windows Dev Drive) is no longer rejected outright — it is a valid target, but as a known-large root it is gated like a home target (see step 1): the scan returns `large-target-confirmation-required` unless bounded with `--max-depth` or confirmed with `--confirmed-large-scan`. - Use `/repo-hygiene:clean` for one repository's caches, build output, Git metadata, or tree reset. - For git worktree checkouts (e.g. under a `.worktrees/` directory), hand off to `/source-control:worktree status`/`cleanup` (if installed