awb-uninstalllisted

# Uninstall the workbench, honestly > **Announce on activation:** "Using awb-uninstall — I'll show you exactly what would be removed first, then remove it only once you confirm." The persona this kit serves often can't read a manifest or diff a settings file, so they can't tell a clean uninstall from one that quietly deleted work they'd changed. The only honest way to remove the kit is to **show the plan before touching anything**, get a clear yes, and then state plainly what was removed and what was *kept*. `uninstall.py` is built for exactly this — it is dry-run by default and never deletes a file you edited. This skill makes the agent use it that way instead of improvising file deletions. ## Scope - **Does:** run `uninstall.py <project>` (dry-run) to get the removal plan, translate it into plain language, get an explicit confirm, then run `uninstall.py <project> --yes` and relay what was removed vs. kept. - **Does NOT:** hand-delete any file (only `uninstall.py` removes anything); remove files you edited since install (those are KEPT by design — see Honesty); guess what to remove when there's no installer-manifest (`uninstall.py` refuses, and so should you). It is a bypassable exemplar, not a gate. ## Precondition `uninstall.py` lives in the **kit folder**, not in the project it was installed into. Run it from the kit checkout, pointing at the adopter project: `python uninstall.py <project-path>`. (Same precondition the install skill documents — the uninsta