fix(release): publish crate and align install docs

[akiojin]

Summary

• Add a real cargo publish step to scripts/publish.sh so future releases actually publish the crate promised by the install docs.
• Replace broken cargo install unity-cli guidance in the README variants and agent bootstrap skill with GitHub Releases or local checkout install paths.
• Align release docs and helper references with the actual release.yml workflow so Issue Failed installation via Cargo #64 does not recur through stale instructions.

Changes

• scripts/publish.sh: run cargo publish after the existing dry-run validation and fix the workflow URL in the completion output.
• README.md and README.*.md: remove the broken crates.io install path and document GitHub Releases plus cargo install --path . from a local checkout.
• .claude-plugin/plugins/unity-cli/skills/unity-cli-usage/SKILL.md: stop auto-running the broken registry install command and point missing-install cases to supported paths.
• RELEASE.md, docs/development.md, CLAUDE.md, .github/workflows/README.md, and specs/migration-notes.md: update release-entrypoint, workflow-name, and verification guidance to match the current repo behavior.
• scripts/e2e-all-tools.sh: replace the stale crates.io error hint with a release-binary hint.

Testing

• bash -n scripts/publish.sh — shell syntax passes.
• git diff --check — no whitespace or conflict-marker issues.
• npx --yes markdownlint-cli README.md README.ja.md README.de.md README.es.md README.fr.md README.it.md README.zh.md RELEASE.md docs/development.md CLAUDE.md .github/workflows/README.md .claude-plugin/plugins/unity-cli/skills/unity-cli-usage/SKILL.md --config .markdownlint.json --ignore-path .markdownlintignore — modified Markdown files pass linting.

Related Issues / Links

• Fixes Failed installation via Cargo #64

Checklist

• Tests added/updated — N/A: docs and release-shell behavior only.
• Lint/format passed (cargo clippy, cargo fmt, svelte-check) — N/A: no Rust or Svelte source changed.
• Documentation updated (if user-facing change)
• Migration/backfill plan included (if schema/data change) — N/A: no schema or data change.
• CHANGELOG impact considered (breaking change flagged in commit) — N/A: no breaking change.

Context

• Issue Failed installation via Cargo #64 reported on March 4, 2026 that cargo install unity-cli failed on Windows because the crate was still absent from crates.io while the repo and skill docs continued to advertise that path.

Risk / Impact

• Affected areas: release orchestration, installation guidance, and agent bootstrap instructions.
• Rollback plan: revert commit a5af788 and cut a follow-up patch release if the new publish step needs to be backed out.

Notes

• The first release that uses this script now requires a valid crates.io login on the machine running scripts/publish.sh.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 69c3d2b6-52ce-480b-b5af-726f1052c572

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch bugfix/issue-64

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}