find-simplificationslisted

# find-simplifications Evidence-backed simplification sweeps for ARLE. The project deletes in waves (flag deletion waves 1–3, the 2026-05-18 pivot that removed 167k LOC) — this skill is the method those waves applied, written down. ## What counts as a strong candidate A strong candidate removes, folds, or demotes something real, with evidence that the current design costs more than it buys: - A flag, config knob, public method, trait method, registry row, or module has no production consumer — `crates/*/src`, `src/`, serve paths, and loader/config paths are the production corpus. - Tests, benches, and docs are the only consumers, and the behavior they pin is not load-bearing. - Two mechanisms mirror the same fact (two knobs for one axis, two code paths for one shape). - A feature implements speculative generality with no product owner: multi-session, background rosters, mid-turn steering, "for later" seams. - Hand-rolled code reimplements what a dependency or stdlib already provides, and the swap deletes the implementation plus its tests. - An invariant, rollback path, or special case exists only to protect an unused API. Thin candidates: one dead symbol, a typo, "this looks complex" without call-site proof. `cargo machete` (nightly) finds unused dependencies; it is not a substitute for reading call sites. ## Survey - Start with the largest production-code deltas. Obvious unused symbols are the floor, not the sweep — duplicated lifecycle and defensive m