openspec-archive-change

To archive openspec changes safely, the workflow validates artifacts and tasks, compares delta specs to main specs, and moves the change directory to openspec/changes/archive/YYYY-MM-DD-<name> while prompting for user confirmation on any uncertainties.

During openspec change archival, the process surfaces incomplete artifacts and tasks using openspec status JSON and a local tasks file, then explicitly requests user confirmation before proceeding with the archive operation to prevent data loss.

To sync delta specs before archiving an openspec change, the workflow compares delta specs under openspec/changes/<name>/specs to main specs, summarizes additions, modifications, and removals, and offers sync or skip options by invoking a sync task if requested.

Yes, the openspec CLI is required to finalize and archive changes because the workflow depends on parsing openspec status JSON output and requires read/write access to openspec/changes and openspec/specs directories to verify artifacts and prepare archival.

Yes, you can choose which active change to archive in openspec, as the workflow provides interactive change selection and prompts the user to select a specific change if no name is provided, preventing accidental archives of the wrong change.

Archived openspec change summaries include warnings when the workflow detects incomplete artifacts, unresolved tasks, or sync status uncertainties during the archival process, ensuring all contextual issues are recorded for long-term reference.