Add release version to the site footer

[mikeylong]

What changed

• Added a shared footer to JudgmentKit’s canonical site pages with a direct link to the current GitHub Release.
• Kept the release label secondary: regular Inter, the site link color, and an external-link cue, with underline and focus treatment during interaction.
• Sourced the displayed version from package.json.
• Expanded production verification across the homepage, Value, and Docs routes.
• Published the missing v0.7.0 Release at the exact 0.7.0 merge commit so the footer link has a truthful destination.

Why

The current release should be visible without competing with page content or reading like developer metadata. The footer now provides a consistent, accessible path from the site to the corresponding repository release.

Validation

• npm test — all repository tests and 8/8 eval cases passed
• node tests/site-local-server.test.mjs
• git diff --check origin/main...HEAD
• Browser QA at 1440×900 and 390×844
• Resting, hover, and keyboard-focus styles verified from computed browser state
• No mobile overflow, console errors, or console warnings

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
judgmentkit-ai	Ready	Preview	Aug 9, 2026 5:58am

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7e84585698

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".