Closes #1081.

Maintains web-client release notes locally in this repo — versioned with the code, bundled into the client, and shown in their own landing-page tab — instead of relying on the central SlideRule docs. Notes are generated from git log at tag time and mirrored to GitHub Releases.

What changed

Release-notes content

• New web-client/src/assets/content/release-notes/ with one Markdown file per version (vX.Y.Z.md), seeded with v4.4.4–v4.5.2 backfilled from their real commit ranges + tag dates.

UI — LandingView.vue

• Tabs are now About · Contact · SlideRule Releases · Web Client Releases.
• SlideRule Releases keeps the existing remote docs scrape (platform/server notes).
• Web Client Releases (new) loads the bundled markdown via import.meta.glob(... ?raw) and reuses the existing marked + DOMPurify list→detail UI. Detail view links "View on GitHub ↗" to the release tag.
• docLinks.ts: added webClient repo/tags links.

Tagging / release tooling

• New gen-release-notes.sh: generates a version's notes from the commit subjects since the previous tag. Idempotent (preserves a hand-edited draft; --force to regenerate).
• New publish-gh-release.sh: mirrors the committed notes to a GitHub Release. Non-fatal — warns and skips if gh is missing/unauthenticated, so it never blocks a deploy.
• VITE_VERSION.sh: generates + commits the notes file before creating the tag, so the tag (and the build's VITE_APP_VERSION) include it.
• Makefile: src-tag-and-push now calls publish-gh-release.sh; added a gen-release-notes target for curating a draft before release.

Docs — README.md: documents the test-first release workflow (release-live-update-to-testsliderule VERSION=… → verify → live-update-slideruleearth) and how release notes are maintained.

Release flow

make release-live-update-to-testsliderule VERSION=v4.5.3   # tag + gen/commit notes + GitHub Release + deploy to test
# verify on testsliderule.org
make live-update-slideruleearth                            # redeploy same tag to production (no re-tag)

The tag, the committed notes file, and the GitHub Release are created once (in the test step); production just rebuilds the existing tag.

Verification

• make typecheck ✓ · make lint ✓ · make test-unit ✓ (194 passed) · make build ✓
• Confirmed the seeded notes text and the new tab label are bundled into the LandingView chunk.
• Generator dry-run, idempotency skip, and the publish-gh-release.sh non-fatal guard all exercised locally.

🤖 Generated with Claude Code