openspec-bulk-archive-change

To batch-archive OpenSpec changes, validate artifact statuses across openspec/changes, read tasks, enumerate delta specs, and move approved changes into a single date-stamped archive directory. This preserves configuration files and generates a per-change status report.

Conflict resolution for delta specs detects overlapping changes by inspecting code evidence and chronology, then applies a deterministic ordered resolution strategy. This ensures conflicting delta specs are consolidated correctly before changes are archived.

Consolidating task lists and artifact states involves validating the status of artifacts within openspec/changes and reading associated tasks. The bulk archive workflow enforces this consolidation to ensure only approved changes are archived with status reporting.

Yes, the bulk archiving process preserves the .openspec.yaml configuration file when moving completed changes to the archive directory. This ensures the archived change retains its necessary OpenSpec workflow configuration.

You should avoid batch archiving when individual changes have unresolved artifact statuses or unapproved tasks. The workflow strictly archives only changes approved for archival, enforcing user prompts to prevent moving incomplete work into the date-stamped archive.