spec-finish

# Spec Finish Post-implementation workflow: simplify → synchronize docs → validate → review → prepare PR. ## Prerequisites Before starting, verify: 1. All Spec-backed Plan tasks are complete 2. Working directory has no unresolved staged or unstaged changes 3. Tests pass If not complete, go back to `spec-implement`. --- ## Step 1: Compare Scope and Simplify Compare the implementation with the original behavior and user goal before documentation or validation. Remove unrequested scope, duplicate concepts, one-consumer abstractions, and custom machinery that replaces sufficient platform behavior. If the implementation faithfully follows an unnecessarily large design, stop and return to `spec-plan`. Get approval for the smaller plan before continuing. Update the finished SDD to describe the smaller result. Replace rejected architecture in the normative design and plan instead of preserving it as precedent; mention it only as a rejected alternative when that history remains useful. --- ## Step 2: Update Documentation Check whether README, API documentation, or changelog updates are needed. Make and commit any necessary documentation changes through **code-commit** before final validation. --- ## Step 3: Validate Run validation checks. ### Test Suite ```bash npm test # or pytest # or cargo test ``` ### Type Check ```bash npm run typecheck # or python -m mypy # or cargo check ``` ### Lint ```bash npm run lint # or ruff check . # or cargo clippy ``` ### Build ```ba...