openspec-archive-change

To archive completed changes, the workflow verifies all artifacts and tasks are complete, assesses specification synchronization, and moves the change directory to an archive location while providing a summary of the operation and any warnings encountered.

Specification sync is the process of aligning delta specifications with main specifications. You need it when archiving completed experimental changes to ensure all modified specifications are up-to-date before the work is permanently moved to the archive.

No, you cannot archive a change directory if tasks are not verified. The archiving mechanism performs status checks to ensure artifact and task completion is fully verified before allowing the directory to be moved.

Yes, the change archiving process provides a summary of the operation and explicitly warns you about any missing artifacts, unverified tasks, or specification synchronization issues encountered during the directory move.

The best way to manage experimental development lifecycle cleanup is to archive completed work by moving change directories to a dedicated location, which ensures a clean workflow and verifies all artifacts and specifications are synchronized.

Yes, a key limitation is that archiving changes with incomplete specification synchronization can result in warnings, as the process assesses and optionally syncs delta specifications with main specifications to prevent outdated archives.