Repo-Wide Dead Code Sweep

"Unused" is a claim about every caller, and most callers are not in the graph an analyzer sees. They are in a scheduler, a database trigger, a template stored at a provider, a build script that iterates over numbered keys, an external website embedding your badge, or a README that says "kept for reactivation". A static analyzer's report is a list of candidates, not a list of deletions.

Deleting is cheap. Being wrong is expensive, because a removed capability is usually rediscovered by a user, weeks later, with no error pointing back at the commit. So the deliverable of a sweep is a dossier first and deletions second, and each deletion ships with the name of whatever covers the capability today.

Quick reference