[P1] Cargo.toml package version (0.1.0) was never bumped for the v0.2.0 release tag

[SoundMatt]

What's wrong

The latest GitHub release/tag is v0.2.0 (2026-06-19, "RELAY v1.10 §12 CLI conformance + adapt/convert"), but Cargo.toml's version field at that exact tag is still 0.1.0:

$ git show v0.2.0:Cargo.toml | head -5
[package]
name = "rcp"
version = "0.1.0"

Because the CLI's version field is derived from env!("CARGO_PKG_VERSION") (src/bin/rcp.rs:62,70), the shipped v0.2.0 binary self-reports as version 0.1.0:

$ ./target/debug/rcp version --format json
{ ... "version": "0.1.0", ... }

This is the field relay probe, relay versions, relay compare, and the release SBOM (§11.2.1) all rely on to identify what's actually running — a tagged v0.2.0 release permanently self-identifying as v0.1.0 breaks that traceability.

Expected per spec

Not itself a RELAY spec requirement, but a basic release-hygiene expectation implied by §20.5 (supply-chain integrity / build provenance) and by every downstream tool that reads the version field as ground truth.

Suggested fix

Bump Cargo.toml's version to 0.2.0 (ideally as part of the tagging step in .github/workflows/release.yml, if it doesn't already do this) and re-tag, or cut a v0.2.1 with the corrected version field.

---

Filed from the RELAY ecosystem audit (2026-07-27), category: bug, severity: P1.