openspec-bulk-archive-change

Batch archiving OpenSpec changes involves selecting multiple completed changes and moving them to the archive in a single operation. The tool validates artifact completion, task states, and delta specs before executing the move.

When archiving parallel changes, conflict detection identifies overlapping delta specs across changes and computes a safe archival order. The tool inspects the codebase to resolve conflicts and applies only implemented delta specs during the archival process.

Using a conflict-aware batch archival tool is the best way to archive changes while preserving metadata. It validates delta specs, resolves conflicts by inspecting the codebase, and ensures metadata is safely moved to the archive.

Yes, the batch archival process validates task states before archiving changes. It assesses artifact completion, task states, and delta specs per change to ensure only eligible active changes are moved to the archive.

If delta specs overlap during batch archival, the tool detects the conflict and computes a safe archival order. It resolves the overlap by inspecting the codebase and applying only the implemented delta specs to preserve history.

You can archive several parallel changes without manual conflict resolution because the tool automatically detects overlapping delta specs. It inspects the codebase to compute a safe archival order and applies only implemented changes.