docs(hemx): define v1 versioning policy

Add a compact semver and upgrade policy for v1: stable beginner APIs, stable wire/runtime compatibility, advanced escape-hatch tier, breaking-change rules, upgrade-note template, and release checklist. req: abi/001 req: abi/002 req: abi/003 req: abi/004 req: abi/005 req: public_api/001 req: public_api/002 req: public_api/005 req: runtime/003 req: runtime/004
2026-06-05 09:49:30 +02:00
parent c8c71deb68
commit 1fbeeb52b8
3 changed files with 152 additions and 1 deletions
@@ -111,6 +111,7 @@ fall back to a full page reload when possible. See `docs/recipes/deploy-versioni
 Before a v1 release, the semver policy and upgrade notes should explicitly state
 which surfaces are stable: beginner generated helpers and handler shapes; the
 wire/runtime ABI; and advanced escape hatches that may remain integration-level.
+See `docs/versioning.md`.

 ## Examples