openspec-bulk-archive-change

To batch archive multiple OpenSpec changes, you select active changes and run a bulk archival process that validates artifacts and tasks before moving them into date-based archive folders. This preserves configuration files while safely resolving delta-spec conflicts.

Delta-spec conflict resolution works by analyzing codebase evidence to detect and resolve conflicts across active changes before archival. This ensures data integrity by verifying that artifacts and tasks align with the actual codebase before changes are archived.

Yes, you need the OpenSpec CLI installed to perform bulk archival of changes. The CLI is required to analyze active changes, validate tasks, and preserve configuration files during the batch-archive operation.

The best way to archive active changes without losing configuration files is to use a bulk archival process that preserves the archive structure with date-based folders. It safely validates dependencies and resolves conflicts using codebase evidence before moving files.

Batch archiving OpenSpec changes saves time and reduces manual overhead compared to individual archival. It analyzes multiple active changes at once, validates artifacts, detects cross-change conflicts, and resolves them using codebase evidence in a single operation.

Yes, you can archive changes with conflicting delta specs because the bulk archival process detects conflicts and resolves them using codebase evidence. This ensures that active changes are safely archived without compromising data integrity.