docs(docs-site): bump VERSION to 0.16.2 and patch /release

The /release command skeleton in .claude/commands/release.md only
touched four version files (CHANGELOG, proxy/migration Cargo.toml,
admin-ui/package.json) and missed docs-site/docs/.vitepress/constants.ts
— the single source of truth for the {{VERSION}} token substituted
across every docs page at build time. v0.16.2 shipped with the docs
site still showing 0.16.1 in install/upgrade instructions. This commit
bumps constants.ts to 0.16.2 (the docs-site deploy workflow is path-
gated, so this commit alone re-triggers it) and adds step 5 to the
/release command so the next release includes it by default.

Author: jumpbetweenrows

.claude/commands/release.md

@@ -58,9 +58,11 @@ Once the user confirms the version and changelog entries:
 
 4. **`admin-ui/package.json`** — Update the `"version": "..."` field.
 
+5. **`docs-site/docs/.vitepress/constants.ts`** — Update the `VERSION` constant. This is the single source of truth for the `{{VERSION}}` token substituted across every docs page at build time (see `docs-site/CLAUDE.md` → "Version-bump checklist"). Forgetting this leaves `docs.betweenrows.dev` showing the previous version in install/upgrade instructions.
+
 ### 5. Commit and tag
 
-- Stage the four files above plus `Cargo.lock` (updated when Cargo.toml versions change) **and any docs-site edits applied in step 2**.
+- Stage the five files above plus `Cargo.lock` (updated when Cargo.toml versions change) **and any docs-site edits applied in step 2**.
 - Commit with message: `Release vX.Y.Z`
 - Create an annotated tag: `git tag -a vX.Y.Z -m "Release vX.Y.Z"`
 

docs-site/docs/.vitepress/constants.ts

@@ -14,4 +14,4 @@ export const OG_IMAGE_URL = `${WWW_URL}/og-image.png`
 // Current released proxy version. Bumped by /release alongside Cargo.toml
 // and admin-ui/package.json. Substituted into markdown via the {{VERSION}}
 // token — see the markdown.config hook in .vitepress/config.ts.
-export const VERSION = '0.16.1'
+export const VERSION = '0.16.2'