[VPDPersonal]

Requested by Vladislav · project thread

Important

• Merge after CI is green; then the v1.0.0-rc.9 tag starts the Release workflow (asked separately)

Why

Aspid.MVVM needs a prerelease with the APIs renamed since 1.0.0-rc.8. Channel upm-preview, version 1.0.0-rc.9: the [Unreleased] notes of both CHANGELOGs become its section.

What

• scripts/set-version.sh 1.0.0-rc.9: package.json, Preview badge, install URLs in both README translations, root README regenerated.
• [Unreleased] → ## [1.0.0-rc.9] — 2026-10-24 in CHANGELOG.md and Website/i18n/ru/CHANGELOG.md, with the release link.
• The section intro said "First stable release": replaced with "The last prerelease before 1.0.0" (EN and RU), since rc.9 is a prerelease. The 1.0.0 release PR (chore(release): v1.0.0 #515) keeps its own CHANGELOG.

Verification

• npm --prefix Website run check-readme: README matches.
• npm --prefix Website test: 101 pass; check-translations ok; scripts/check-version.mjs ok; scripts/package-changelog.mjs v1.0.0-rc.9 ok.
• Not run locally: dotnet test and the DLL rebuild (the .NET SDK download is blocked in the cloud session) and Unity EditMode (no Editor). No code changed since main (docs(website): update Package sample sections for the new samples #550); CI on this PR covers them.
• Old version in prose, left as is: Website/docs/13-agent-skills.md:10,45 and its RU copy ("releases up to and including 1.0.0-rc.8 do not ship the skills": still true).

---

Generated by Claude Code

[claude]

Verdict: 0 blocking, 0 minor

Version files, badge, both CHANGELOG sections and release links are consistent for 1.0.0-rc.9; install URLs point at the upm-preview branch, so they needed no change.