v0.5.0

v0.5.0: Full opsx workflow parity

This release closes cospec's workflow-parity gap with OpenSpec 1.5.0's opsx command set: five new generated agent workflows — including the /cospec:verify command a user reported missing — are now rendered across every supported harness, each adapted to cospec's typed, gated model. It also documents a mise install gotcha that made fresh releases look "not found".

Added

• Full opsx 1.5.0 workflow parity (#23 by @replygirl) — prompted by a report that /cospec:verify was missing from the generated harnesses, this audits the whole opsx 1.5.0 workflow set and brings cospec's generated commands and skills to parity. Each is generated for the Claude, Codex, and OpenCode harnesses (as slash commands and/or skills):

  workflow	what it does
  /cospec:new	scaffolds a change and shows its typed artifact plan, then stops before authoring
  /cospec:ff	fast-forwards an already-scaffolded change through every remaining artifact and validates
  /cospec:verify	dress-rehearses a change: cospec validate --strict, walks the verification ledger, and names the two hard archive gates (archive/verification-incomplete, archive/scenario-preservation) — no --force escape hatch
  /cospec:bulk-archive	archives a batch of completed changes in dependency order, one gated cospec archive call at a time
  /cospec:onboard	walks a first-time user through one real change end to end via the real CLI path

  Every rendered workflow body — new and existing — is scanned to confirm it contains no bare openspec invocation and no manual mv/mkdir of an openspec/changes/ entry: all change-lifecycle operations route through cospec subcommands. opsx's sync workflow is intentionally not a new command (it maps 1:1 onto the existing sync-specs skill), and opsx's update path and feedback loop are deliberately out of scope pending a proper design pass.

Documentation

• mise release-age cooldown note (#22 by @replygirl) — investigation of a reported @aligned-team/cospec@0.5 not found install failure traced the issue entirely to the mise client, not cospec's release pipeline: mise's github backend applies a default minimum_release_age cooldown that hides just-shipped releases from "latest"/fuzzy resolution, and a partial pin like @0.5 never matches cospec's exact 3-part tags. Every documented mise use github:aligned-team/cospec snippet now carries a note explaining the cooldown and recommending an exact-version pin (e.g. @0.5.0) when testing a fresh release.

Full Changelog: v0.4.0...v0.5.0