v0.1.1

v0.1.1: Unblock the release pipeline

A maintenance release that repairs the automated release/publish workflow after the v0.1.0 dispatch failed to publish to npm. There are no application code changes — this release exists to get cospec reliably onto npm.

Fixed

• npm publish path classification (#11 by @replygirl) — npm publish was handed a bare relative tarball path (npm-dist/<pkg>.tgz), which npm's argument classifier treats as GitHub owner/repo shorthand, causing it to attempt an SSH git ls-remote and fail with Permission denied (publickey). Publishes now pass a ./-prefixed path, forcing the correct local-tarball interpretation.
• Safe failure rollback (#11) — the cleanup job previously deleted the GitHub release on any failure, which in the v0.1.0 incident tore down an already-public release while a tag-protection ruleset kept the dangling tag. Rollback is now gated on npm liveness: it checks all eight packages (main + seven platform packages) and only removes the tag/release when nothing is live, otherwise leaving everything intact for a clean resume.
• Resumable release dispatch (#11) — the version job's tag-exists guard now distinguishes a genuine conflict (tag on a different commit) from a safe resume (tag on the current bump commit with the package not yet published). The resume case proceeds and finishes the remaining publishes; the conflict case still fails.

Full Changelog: v0.1.0...v0.1.1