tidylisted

# Tidy A cleanup nobody can verify is a cleanup nobody should merge. Tidy exists so that the sentence "this file is not used" becomes a checkable claim instead of a hunch, and so that acting on it is always reversible. ## The two halves **Mechanical, and therefore a script.** Whether a file is byte-identical to another, whether git's own ignore rules already match it, whether any entry point reaches it through resolved imports, how long since a commit touched it, how many bytes it costs every clone. `tidy-scan.ts` answers all of that and emits evidence. No model judgment is involved, so the answer is the same on every machine and in CI. **Judgment, and therefore yours.** Whether the repo actually wants that file gone. Whether a folder named `legacy/` is dead weight or a deliberate archive. Whether a script with no importers is abandoned or is the deploy hook someone runs by hand once a quarter. The scan gives you the facts and a confidence; the decision, and the interview that informs it, are the model's job. Keeping those halves apart is the whole design. When the model guesses at the mechanical half, it hallucinates dead code. When the script decides the judgment half, it quarantines the deploy hook. ## Why nothing is ever deleted Deletion is a claim that the future will not need something, made by whoever happens to be looking today. Tidy refuses to make that claim, and does not need to: git history plus a quarantine directory make "gone from where it was" and "gone