chore(release): begin 0.25 development and publish 0.24 article (#1674)

.codex/skills/release-cut/SKILL.md

@@ -73,11 +73,12 @@ the complete 27-asset set documented in `docs/architecture/release-pipeline.md`.
 It is read-only, and fails on an already-published release. Still review the
 authored text and generated commits by eye.
 
-After verification, manually publish the GitHub release. That publication
-automatically verifies its Snap assets and uploads them to `edge`.
-Installed-Snap smoke and candidate/stable promotion remain manual. Keep the
-blog draft during artifact verification; publish it in a follow-up commit and
-verify the website deployment.
+Manually publish the release; this verifies and uploads Snaps
+to `edge`. Installed-Snap smoke and candidate/stable promotion stay manual.
+After public-asset verification, publish the draft blog and update
+`apps/website/released-version.json` to the published version together.
+Follow the release pipeline's offline-download checks and verify deployment;
+never use the development/nightly version for this pin.
 
 ## Failure Safety