spectra-archivelisted

Archive a completed change. **Input**: Optionally specify a change name after `/spectra-archive` (e.g., `/spectra-archive add-auth`). If omitted, infer it from conversation context when exactly one active change is clearly identified. Only prompt for available changes when no name can be inferred or multiple candidates remain. **Prerequisites**: This skill requires the `spectra` CLI. If any `spectra` command fails with "command not found" or similar, report the error and STOP. **Steps** 1. **Select the change** If the name is clear from the input or conversation context, use it directly. Otherwise, run `spectra list --json` to get active changes and use the **AskUserQuestion tool** to let the user select. Show only active changes and include the schema used for each change when available. Do not guess when multiple candidates remain. Before reading status or constructing any path, run `spectra list --json` and require the selected value to be an exact active change name returned by the CLI. Reject names containing path separators, `..`, or any value that does not match `^[a-z0-9]+(?:-[a-z0-9]+)*$`; never use an unvalidated argument as a filesystem path. 2. **Check artifact completion status** Run `spectra status --change "<name>" --json` to check artifact completion. Parse the JSON to understand: - `schemaName`: The workflow being used - `artifacts`: List of artifacts with their status (`done` or other) **If any artifacts