archive-speclisted

# Archive Spec Move a completed spec out of the active set: `docs/specs/<slug>/` → `docs/specs/_archived/<slug>/`, with the completion stamped in its frontmatter. Archived means _implemented, verified, and self-contained_ — every task done, QA passed, and every indexed reference owned by the Spec — after this, one `ls docs/specs/` separates live work from history, and the archive stays greppable as the record of what was built and why. The trigger is spec completion, not publication: run this automatically at the end of the `implement-spec` loop once the QA gate passes, or whenever the user asks. Merge and release are separate, user-driven steps — the archive commit simply travels with the branch and ships inside the feature's own PR. ## Preconditions — verify, don't trust Check all three with fresh command evidence before touching anything: 1. **Every task completed.** Read each `task_NN.md` listed in `_tasks.md`; every `status` must be `completed`. **Command:** run `grep -n '^status:' <each-task-file-listed-in-_tasks.md>` and retain its output. Any value other than `status: completed` blocks the archive and names the Task file. 2. **QA passed.** The newest report in `qa/` must pass the repository's QA verifier. Do not substitute a line grep for structured validation. In Roundfix, use the same `internal/spec.QAVerdict` contract as the Archive Command: select the newest report by the `qa-report-YYYY-MM-DD[-NN].md` filename contract, parse its YA