repo-hygiene-sweeplisted

# repo-hygiene-sweep A fleet sweep finds work before it changes work. Begin with a read-only inventory, classify each target, discover its own gates, and review only targets that are safe to inspect. A finding is a claim with evidence, not a reason to edit. ## When to use - A group of repositories needs a hygiene review before a repair, handoff, or ownership change. - You need one report that distinguishes safe work from dirty, archived, generated, vendored, untested, or unreadable targets. - You need findings routed for later action, not a batch of unapproved edits. ## Required inputs - The fleet roots and the scope of the sweep. - Read access to each target and its git state, when it has git metadata. - Explicit authority for any mutation or external action beyond reading and approved local checks. ## Steps 1. Fleet inventory. Build a read-only inventory of every target. Record its root, git state, branch when present, and visible ownership or archive markers. Do not edit during inventory. 2. Topology classification. Classify each target as active, dirty, archived, generated, vendored, untested, or unreadable. Protected target rules mean: - Do not edit a dirty target. - Do not edit an archived target. - Do not edit a generated target. - Do not edit a vendored target. - Do not edit an untested target. - Do not edit an unreadable target. 3. Workflow gate discovery. Read each target's contributor rules, CI, scripts, and test setup. Use only