sdd-plan-refactoringlisted

# Plan SDD refactoring 1. Fix target, limits, and slug. Resolve `tasks/prd-[slug]/prd.md` and `techspec.md`. Preserve both when they exist without update authorization; with it, read current versions and keep IDs. **Output:** unambiguous operation without implicit overwrite. 2. Trace inputs, outputs, errors, effects, callers, persistence, integrations, and edges of the target. Use code, tests, logs, and contracts as evidence. Number behaviors `R-01`, `R-02`; distinguish intent, apparent defect, and gap. **Output:** every in-scope behavior has an origin and verification, or a concrete question that changes acceptance. 3. Plan characterization only for behavior without protection; prefer semantic assertions. A Golden Master/snapshot requires a reviewed baseline. Sequence characterization before mutation and reversible slices before irreversible changes. For WinForms/DevExpress, read [references/winforms-devexpress.md](references/winforms-devexpress.md) in full. In any desktop C#/.NET, omit E2E; record existing unit/integration projects, runner, and commands, plus a manual script for uncovered visual behavior. Record an unavailable environment as pending. **Output:** every `R-NN` has a proportional safety net and safe sequence; new behavior is separate from scope. 4. When drafting, read [assets/TEMPLATE_PRD_REFACTOR.md](assets/TEMPLATE_PRD_REFACTOR.md) and [assets/TEMPLATE_TECHSPEC_REFACTOR.md](assets/TEMPLATE_TECHSPEC_REFACTOR.md) in full. Write only the two artifa