openspec-archive-change

To archive completed openspec changes, you finalize the change into a date-stamped directory under openspec/changes/archive. This preserves the .openspec.yaml metadata and history while keeping the working directory clean for future reference.

Validating artifact status before archiving uses the openspec CLI to check task completion. The process surfaces warnings about incomplete artifacts without blocking the archiving operation, ensuring safe finalization of experimental workflow changes.

Syncing delta specs before archiving involves assessing synchronization between delta specs and main specs. The archiving process optionally performs a sync prior to the move and provides a summary indicating whether syncing occurred.

Archiving openspec changes relies on the openspec CLI to perform artifact status checks and execute the directory moves. The CLI enforces the date-based archive path and preserves the .openspec.yaml configuration during the operation.

When moving finished openspec changes to the archive directory, the .openspec.yaml metadata file is preserved. The archive path is date-based, ensuring structured history and enabling auditability of experimental workflow changes.

You can archive openspec changes even if artifact status validation surfaces warnings. The process checks artifact statuses and task completion before archiving but does not block the operation, allowing finalization while flagging potential issues.