Machine Cleanup — Orchestrator

Audits a developer's machine state and removes abandoned tools, orphaned caches, and unused toolchains — without breaking active workflows. Capability metadata (route triggers, prerequisites, load map, artifact contract) lives in routing.yaml. Agent table + execution layers + routing rules: references/agent-manifest.md. Methodology: references/playbook.md.

Core question: Is this folder still owned by an installed tool I actively use, or is it leftover state from something I no longer have?

When To Use

• New laptop setup; need to start clean.
• After trying many AI tools you've now abandoned.
• Disk is full or near-full.
• Before passing the machine to someone else.
• Standalone — no upstream gate required.

When NOT To Use

• Cleaning source code → /clean-code.
• Triaging files in Desktop/, Documents/, Downloads/, Pictures/, Movies/, Music/, Public/, or cloud-mount symlinks — those need human review.
• Tool ownership unclear AND you can't identify the owning tool — surface as NEEDS_CONTEXT first.