resetlisted

# organic-os reset (guided teardown) organic-os never deletes anything irreversible automatically. This skill walks the user through everything that exists for a site and what to do about each piece, then only touches the local registry with explicit confirmation. ## Step 1: show what exists 1. Read `~/.config/organic-os/sites.yaml` via `core.registry.load()`: list every registered site (slug, name, url, brain path) and which one is active. 2. List files in `~/.config/organic-os/` - the per-site env files (`<slug>.env`, holding `WP_APP_PASSWORD` / `TELEGRAM_BOT_TOKEN`) and the registry file itself. 3. For the site the user is asking about: report whether its brain path exists on disk and whether it is a git repo (has a remote or not). ## Step 2: ask which site to tear down AskUserQuestion: which registered site (or "all"). Confirm before any write. ## Step 3: walk through each piece, per site Only item 2 below is something this skill performs, and only with explicit confirmation. Everything else is the user's own action - state why for each. 1. **Scheduled routines**: point at the runtime's own mechanism. If runtime mode is `claude-scheduled`, tell the user to remove the scheduled task from their Claude scheduler. If `ci`, tell them to disable/delete the workflow file or cron entry in their CI system. organic-os does not manage the runtime's own scheduler and cannot deregister a routine for them. 2. **Registry entry**: with explicit confirma