prep 0.9.3 release, following the htmx pattern to avoid missing things

Author: 1cg

CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-## 0.9.92 - 2026-06-26
+## 0.9.93 - 2026-06-26
 
 Bugfixes and follow-ups from the 0.9.90/0.9.91 release:
 

dev/RELEASE.md

@@ -0,0 +1,33 @@
+# Release checklist
+
+* Ensure `CHANGELOG.md` is updated with the new version + date
+* Bump the version BY HAND in both places (the bundle version is not derived
+  from the build, so both must be kept in sync):
+  * `package.json` (`version`) -- then `npm install` to sync `package-lock.json`
+  * `src/_hyperscript.js` (the `version:` field)
+* Build dist: `npm run dist`
+* Update SHAs: `npm run update-sha`
+  * reads the version from `package.json` and writes `www/_data/integrity.json`
+    (`{version, min, full, esmMin, esm}`), the single source of truth the site
+    injects into CDN snippets via the `__VERSION__` / `__SRI_*` tokens
+* Copy dist into the site: `npm run www` (builds + copies `dist/*` to `www/js/`)
+* Run the checks:
+  * `npm run release-check` (dist matches src, integrity.json matches dist + package.json, node validator boots)
+  * `npm test` (and `npm run test:all` for all browsers)
+* Commit all changes (including `dist/`, `www/js/`, and `www/_data/integrity.json`)
+* Tag: `git tag X.Y.Z`
+* Push, including tags: `git push && git push --tags`
+* `npm publish`
+* (optional) GitHub release:
+  ```bash
+  gh release create X.Y.Z --title "X.Y.Z" \
+    --notes "$(sed -n '/## X.Y.Z/,/## /p' CHANGELOG.md | sed '$d')"
+  ```
+* Announce
+
+## Notes
+
+* The CDN version/SRI shown across the docs come from `www/_data/integrity.json`.
+  Do NOT hand-edit version pins or `integrity="..."` in docs -- use the tokens
+  `__VERSION__`, `__SRI_MIN__`, `__SRI_FULL__`, `__SRI_ESM_MIN__`, `__SRI_ESM__`,
+  which `www/eleventy.config.mjs` substitutes at build time.