tidylisted

# /tidy Finds what's rotting in your workspace and fixes it. Not just broken refs — ghost names, stale lessons, duplicate data, language drift, dead code. ## When to use - "Things feel messy" - "Clean this up" - "Prune" - After a big refactor when docs have drifted - Periodically, to keep the knowledge base honest - Before a release, to make sure everything is true ## On invoke 1. Run `atris clean --dry-run` silently. Collect results. 2. Read atris/MAP.md, atris/TODO.md, atris/lessons.md, and today's journal. 3. Scan for these problems (in priority order): ### What to look for **Ghost names** — terms that don't match the current identity. Check package.json `name` and `description`, README title, and PERSONA. Grep the codebase for old names (e.g., "atrisDev" when the product is "atris"). Flag any user-facing string that uses a dead name. **Stale wiki pages** — pages with `last_compiled` frontmatter where the source files have been modified since. The page content may be wrong. **Broken MAP.md references** — file:line refs that point to code that moved or was deleted. The auto-healer fixes what it can; report what it can't. **Stale lessons** — lessons about bugs that have since been fixed. Grep the named files for the bug pattern. If it's gone, tag the lesson `[resolved]`. **Duplicate scorecards** — same slug appearing twice in scorecards.md. Keep the one with more data, delete the other. **Abandoned tasks** — in-progress tasks claimed more than 3 days ago. Either