openspec-bulk-archive-change

Batch archiving completed changes requires validating active changes, grouping them, and archiving them under a dated path in one operation. This reduces manual overhead and keeps change history organized.

Code evidence resolves spec conflicts by aligning implementation deltas with the actual code changes. During batch archiving, the system identifies conflicts and uses the code evidence to intelligently align deltas before archiving the completed changes.

Yes, bulk archiving validates active changes and presents clear selection options. You can select all active changes or specify which completed changes to include before confirming the batch archive operation.

The best way to tidy up completed changes is batch archiving, which handles spec conflicts intelligently and enables optional spec synchronization. This provides safe, auditable archival while keeping change history organized.

No, you do not need to resolve spec conflicts manually before archiving. The batch archive process handles spec conflicts automatically by aligning deltas with implemented code evidence during the archival operation.

You should avoid bulk archiving when active changes are incomplete or unresolved conflicts exist without clear code evidence. The process relies on validating completed changes and aligning implementations, so incomplete changes may cause archival failures.