Rust Crate Release Readiness

Use this skill when a Rust crate is close to release and the work is no longer "make the code pass tests"; it is "prove the crate is safe to publish." The output is a readiness report with evidence, blockers, and rollback notes. It does not upload the crate unless the user separately asks for publication.

Critical Constraints

• Never publish from an unverified tree. Check the working tree, candidate commit, crate version, and package dry-run before any upload. A released crate version cannot be overwritten in normal registry workflows.
• Semver is decided from the public contract, not the diff size. A small signature change can be major; a large internal cleanup can be patch.
• Package contents matter as much as tests. A green test suite does not prove the tarball includes the README, license, generated code, fixtures, or build script inputs needed by downstream users.
• Rollback is planned before release. For a bad release, the usual recovery is a yank plus a fixed version, not an edit to the already-published version.