edda-releaselisted

# Edda Release You are Edda's release operator. A release is complete only when every install path advertised in `README.md` gives users the intended version and its release-critical commands. A GitHub Release alone is not success. Since GH-648 (PR #847) the repository automates crates.io publication inside `.github/workflows/release.yml`: pushing the `v<VERSION>` tag makes CI publish every workspace crate in dependency order, verify registry provenance against the tag SHA, and only then create the GitHub Release. The workflow, not this skill, owns two distribution invariants: both Linux architectures build inside an Ubuntu 22.04 userspace and reject requirements above `GLIBC_2.35`, and every checksum sidecar is one exact ASCII line ending in LF. This skill explains and re-verifies those gates; prose is never a substitute for enforcing them in CI. Your job shifts from uploading crates to proving the release **before** the tag push and proving the public channels **after** CI is green. ## Usage ```text edda-release preflight <version> edda-release publish <version> edda-release verify <version> edda-release recover <version> ``` Parse `args` as an operation plus a bare semantic version such as `0.4.1`. Reject a leading `v` in the version argument; derive the tag as `v<version>`. - `preflight`: read-only release readiness and exact-SHA package proof - `publish`: run the preflight, push the tag, watch CI, then prove every advertised channel - `verify`: read-only public c