Deslop

Goal

Three finders, one per altitude, build a concise fix plan over one declared scope. Each finder's brief defines its altitude in full:

• Slop, per SLOP-BRIEF.md: the residue agent-written code leaves behind.
• Structure, per STRUCTURE-BRIEF.md: code-judo moves that make whole branches, flags, wrappers, or layers disappear.
• Prose, per PROSE-BRIEF.md: comments, docstrings, and in-scope docs the code has outgrown.

High conviction over coverage: a plan of the moves worth making beats an inventory of observations. Prose is the exception. Every comment or docstring that is not load-bearing is a row, so that section runs long.

Hard Rules

• Three finders, one wave. Dispatch exactly one finder per altitude, each over the whole scope, all together and exactly once. With the user, narrow any scope one finder cannot read whole.
• Read-only until the user accepts the plan.
• Behavior unchanged. Every planned fix preserves behavior except a clear bug fix, whose plan row declares the behavior change.
• Not a linter. The plan carries nothing a compiler, type-checker, formatter, or linter catches, and no matter of taste.
• Required behavior stays. Trust-boundary validation, data-loss and error paths, security checks, and accessibility affordances are required behavior, and each brief's never-cut section governs.