openspec-bulk-archive-change

Run the bulk archive workflow, which lists all active changes via openspec list and prompts you to multi-select the ones to archive. After reviewing a consolidated status table, you confirm once and every selected change is archived with its delta specs synced.

The workflow builds a capability-to-changes map and flags any capability touched by two or more changes. It then searches the codebase for implementation evidence: if only one change is implemented, only its specs sync; if both are implemented, they apply in chronological order.

Yes. If the work lives in a registered store, the workflow runs openspec store list --json to discover store ids and passes --store <id> to the commands that read or write specs and changes. Without a store, commands act on the nearest local openspec root.

Incomplete changes appear with warnings in the status table showing unfinished artifacts and task counts. At confirmation you can archive everything, archive only ready changes and skip the rest, or cancel the entire batch.

A delta spec is excluded from sync when conflict resolution finds no implementation evidence for it in the codebase. The change itself can still be archived, and each excluded delta is reported as sync skipped with the change, capability, and reason.