openspec-bulk-archive-change

Batch archiving completed OpenSpec changes moves multiple finished changes into an archive simultaneously while preserving metadata, delta specs, and timestamps. The operation validates statuses, resolves conflicts, and records per-change outcomes for full auditability.

When parallel OpenSpec changes conflict during bulk archiving, a conflict-aware workflow validates each change against delta specs and codebase evidence. Conflicting changes are flagged and must be resolved before the archive operation proceeds, ensuring the original structure remains intact.

Bulk archiving requires validating statuses before proceeding, so changes with incomplete or invalid statuses cannot be archived together. You must select changes, validate their completion statuses, and resolve any conflicts before archiving them as a batch operation.

Bulk archiving is needed when managing parallel OpenSpec changes that must be archived together to maintain lineage. It simplifies change lifecycle management by processing multiple completed changes in a single operation while preserving history and auditability for the entire batch.

Batch archiving preserves the original OpenSpec structure and records per-change outcomes for auditing. Metadata, tasks, delta specs, and timestamps are retained during the move to the archive, ensuring full traceability of each change within the archived batch.