diff-minimizerlisted

## What It Does Evaluates a proposed implementation outline step-by-step against the acceptance criteria. Classifies each step as `ac-satisfying`, `necessary-setup`, `scaffolding`, or `over-build` and recommends which scaffolding and over-build steps to drop before any code is written. The goal is to move scope-creep detection upstream from post-implementation review into the planning phase. ## Use This When Use this between `acceptance-criteria-gen` and the Story Designer's solution write-up, in the graduated and full lanes. Skip in the fast lane — the overhead is not justified for low-complexity work. ## Inputs - Read the acceptance criteria artifact first; identifiers must be `AC-{fr}.{n}` so each step's mapped AC is unambiguous. - Read the proposed solution outline (steps, files to modify, abstractions introduced). - Read canonical module docs at the module paths listed in `module_doc_paths`. Patterns declared there are project conventions and cannot be classified as `over-build`. - Read `references/classification-guide.md` before assigning any classification so the rubric stays consistent. ## Procedure 1. Run `scripts/extract-ac-ids.sh <ac-file>` to load the canonical AC id set; cross-check every cited id against this set. 2. Parse the proposed solution into discrete steps (one new file, one function, or one significant edit each). 3. Classify each step using `assets/classifications.txt` (`ac-satisfying`, `necessary-setup`, `scaffolding`, `over-build`). 4. For `s