openspec-archive-change

Archiving completed changes involves validating that all artifacts, tasks, and delta specs are finished before moving the directory to openspec/changes/archive. The system enforces a date-prefixed naming convention, preserves metadata like .openspec.yaml, and provides a clear summary of actions taken.

When incomplete artifacts or delta specs are detected during openspec archiving, the system prompts for user decisions. It validates all associated tasks to ensure completeness before proceeding to finalize and store the change directory in the archive.

Yes, the archiving process explicitly preserves metadata like .openspec.yaml when storing completed changes. This ensures reproducibility and traceability of the workflow by maintaining all original configuration alongside the archived artifacts and delta specs.

Validating delta specs before archiving ensures that all associated tasks are fully complete and the workflow remains reproducible. The system checks these artifacts to guarantee only finished changes are finalized and stored in the archive directory.

Yes, the openspec archive process enforces a date-prefixed naming convention for directories stored under openspec/changes/archive. This ensures organized storage and traceability of finalized changes.