openspec-archive-change

To archive a completed change, the workflow moves the change directory to openspec/changes/archive with a date stamp. It checks artifact completion and delta spec synchronization before finalizing the move and displaying an audit summary.

When finalizing an openspec change, the workflow verifies artifact completion and assesses delta spec synchronization. It issues warnings if checks fail but does not block the archive process, preserving the original directory for traceability.

No, you do not need a fully synchronized delta spec to archive an openspec change. The workflow warns about incomplete artifacts or unsynchronized delta specs but permits the archive, moving the directory to a timestamped canonical location.

You should use an archive workflow for change management when implementation is complete and you need to finalize work. It moves experimental changes to a canonical archive with a date stamp, ensuring traceability and audit-readiness.

Yes, you can archive an openspec change without specifying the name. The workflow prompts for a target change name if missing, then proceeds to check status, archive the directory with a date stamp, and report the final location.