speckit-archive-cleanuplisted

# SpecKit Archive Cleanup ## Inputs Accept a SPEC-ID such as `DOC-007` or `PRSG-014`, an active spec directory, a workflow file path, or a merged PR URL/number. If more than one is provided, cross-check that they all point to the same completed work. Required facts before editing: - merged PR number, merge timestamp, merge commit, and PR title - active spec directory under `specs/` - workflow file under `docs/ai/specs/.process/`, if present - current roadmap and traceability files affected by the spec family - installed archive extension contract, if `.specify/extensions/archive/` exists ## Ground Truth Checks Start from live repository truth: 1. Inspect `git status --short --branch`. 2. Confirm the current branch is a cleanup branch based on the current mainline, or create one before editing. 3. Confirm the PR is merged with GitHub tooling or the best available local merge evidence. 4. Read the existing newest archive reports in `.specify/memory/archive-reports/` to match local conventions. 5. Check whether `.specify/feature.json` exists. If it is absent, do not create it. If it exists and points at the completed spec, remove or rewrite it only according to repository convention. 6. List active specs with `find specs -mindepth 1 -maxdepth 4 -print` and identify the exact folder that belongs to the merged spec. Do not remove any active spec folder until merge provenance and recovery commands are recorded. Do not remove process files under `docs/ai/sp