What problem does it solve? Finalizing a completed change in an OpenSpec-based workflow requires merging delta specs into main specs, annotating design documents, moving the change directory, committing exact paths, and delivering the branch remotely. Doing this manually risks inconsistent state, mixed commits, and skipped confirmations. ## Core Features & Use Cases - Guarded Archive Execution: Runs entry-state verification (phase, verify_result, confirmation flags) before any archive operation, and blocks on mismatched bound branches. - Delta Spec Merge: Invokes OpenSpec archive to merge ADDED/MODIFIED/REMOVED/RENAMED delta semantics into main specs, with a guard against leaked delta-only section headings. - Controlled Delivery: Requires explicit user confirmation before archiving, then commits only attributable paths and pushes or creates a PR per the user's selected delivery method. - Use Case: After verification passes on a change branch, invoke /comet-archive to confirm delivery, merge the delta specs into main specs, create the single archive commit, and push the bound branch or open a PR. ## Quick Start Ask the assistant to run /comet-archive for the verified change to confirm archiving, merge its delta specs, and push the archive commit.