Proposal: adopt-single-release-channel
Artifacts
Official change artifacts tracked under openspec/.
The release train ran two channels: publishable work landed on main, but semantic-release published only when an owner advanced the beta branch and pushed it, cutting 0.1.0-beta.N prereleases to npm's beta dist-tag. The beta branch was a second moving part with no countervailing benefit:
Affected capabilities
Capability specs this change proposes to modify.
Every publishable @pdpp/* npm package in the reference implementation SHALL use the same semantic-release-governed npm publishing and versioning policy: a single release channel publishing 0.x versions from main to npm's default latest dist-tag.
The reference deployment-diagnostics dashboard surface SHALL render the bound collector's protocol version, runner version, and bundled connector versions alongside the existing runtime-capabilities bindings list, so an operator can see whether a paired collector is compatible with the running reference server.