openspec-bulk-archive-change

Batch-archive completed changes by validating active change sets, resolving spec conflicts by inspecting delta specs and code evidence, and moving changes into a dated archive directory. It processes multiple sets in parallel and reports per-change outcomes.

Conflict-aware spec syncing works by scanning delta specs and matching them against actual code evidence in the repository. This determines what is truly implemented before safely moving the resolved changes into the archive directory.

The best way to archive multiple changes is using an automated batch operation that moves completed changes to a dated directory while explicitly preserving essential configuration files, ensuring safe archival without losing active project settings.

Yes, you can archive multiple change sets in parallel. The process validates active changes, inspects delta specs and code evidence to handle conflicts, and reports individual per-change outcomes to ensure codebase integrity.

When batch archiving encounters spec conflicts, it inspects delta specs and code evidence to determine the actual implementation state. It then resolves these conflicts automatically before moving the completed changes into the archive.