swarm-ejectlisted

# swarm-eject — leaving cleanly Ejecting is not `rm -rf`. A project is wired in six places, and a partial removal leaves the user worse off than never installing: a marker with no registry entry, instruction files still pointing agents at a vault that no longer has the project, hooks firing into nothing. The `eject` command does the work; this skill runs the conversation. ## 1. Ask which exit they want Lead with the recommendation. Most people asking this want **unwire**, not deletion. | mode | what happens to the knowledge | reversible | |---|---|---| | **unwire** *(default, recommend first)* | stays in the vault; the project just stops being wired | yes — `register` brings it back | | **export** | copied into the repo at `docs/swarmvault-archive/`, then removed from the vault | via those files | | **purge** | deleted | only from the backup | If they say something like "remove SwarmVault from this project," that is **unwire** unless they explicitly say delete. Ask before assuming otherwise. ## 2. Show the inventory before doing anything The command's default is a dry run, so run it plainly and read the output back: ```bash swarmvault.py eject --project <P> --mode unwire|export|purge ``` It prints what leaves and what stays: note counts per vault folder, total size, the exact instruction files and hooks to be unwired, and — for export and purge — every inbound `[[wikilink]]` from other projects that would go dead. Surface the orphan warning to the user; it is the on