sdd-create-techspeclisted

# Create SDD TechSpec 1. Resolve `tasks/prd-[slug]/prd.md` and `techspec.md`. Require the PRD; if missing, point to `sdd-create-prd`. Read the PRD once per version. Reuse an existing TechSpec; update only when authorized, preserving IDs. **Output:** exact sources and destination, with no implicit overwrite. 2. Map every PRD obligation to a technical consequence. Inspect only involved modules, callers, contracts, persistence, errors, tests, and configuration. Reuse existing patterns; justify new dependencies and components with a proven gap. Consult primary documentation for external technical questions. Measure the terrain where the change will land: read [references/preparatory-refactoring.md](references/preparatory-refactoring.md) in full and apply its measures to the files the feature will modify. The result is the baseline of pre-existing hits and, when structural debt and contact coincide, a preparatory refactoring recommendation with minimal scope. Existing code the feature only reads generates no recommendation. **Output:** every obligation has a decision or pending item; every component has a path, responsibility, and integration; every target file has a measured baseline and a destination for the debt found. 3. Identify the stack per affected project. For C#/.NET, read [references/dotnet.md](references/dotnet.md) in full before specifying validation. In desktop .NET, omit E2E execution and record `E2E: omitted by desktop .NET policy`; preserve acceptance wi