Use vMAJOR.MINOR.PATCH for site releases and a short descriptive GitHub Release title. Major marks a redesign/platform era; minor marks a named feature milestone; patch marks a focused fix or small improvement within the current milestone. This is a website release convention, not a package API compatibility promise. This recommendation awaits John's release review; it does not create a tag.

Item	Convention / recommendation
Browser exclusion #66	v2.0.1 — Cleaner analytics, proposed next available patch
Mentoring #54	v2.1.0 — Mentoring, preserving its reservation
Optional staging candidate	v2.0.1-rc.1, then -rc.2 when useful
Feature branch	feat/66-exclude-own-traffic from current main
Fix / cleanup branches	fix/<issue>-<short-name> / chore/<short-name>
Version source	Annotated Git release tag at the verified production commit; npm command manifest stays unversioned

Only the historical Ver1 tag/release existed at inspection. Preserve it. October 2 V2 launch and October 14 initial dashboard are documented unversioned deliveries; do not invent old tags or dates.

Maintain CHANGELOG.md in source. Add user-visible entries under Unreleased during feature work. At release, move only the shipped entries to the selected version/date and publish matching GitHub Release notes with the actual production SHA, previous SHA, validation/deployment evidence, limitations and rollback. Never move a published tag.

CI build success, staging review, Pages deployment and the protected Cloudflare Worker are separate evidence. For #66, public Admin and the control page ship via Pages; the private dashboard shortcut needs a reconciled Worker asset deployment. If the shortcut is deferred, disclose that and keep its work open. No final tag or release is published by draft PR #67.

Exclude this browser / Undo stops future collection while preserving consent. Available through the existing consent panel and an always-untracked preferences page. Mark each browser/device and production/staging separately. Clearing storage/private browsing can remove the setting. Earlier visits remain in reports; no owner identity or historical report filter is introduced.

See PR #67, #66, and the release guide. Local analytics/exclusion regressions and all six protected backend tests passed. After integrating the runtime prerequisite as e7200fce37cfd4a6578bd2eda164a7e9b6324fc7, frozen CI 39679233765 and exact-source live staging 39679279467 passed. Browser checks verified exclusion persistence, no Google tag on ordinary excluded pages, an always-untracked management page, Undo with declined versus accepted consent, and Enter-key activation. Physical-device/narrow-layout and full network inspection were not claimed. The protected Worker shortcut and coordinated feature release remain pending.

A separate protected staging dashboard is tracked in #68, estimated at 6–10 engineering hours once account access is ready. The live dashboard already reports staging traffic; independent staging of its code/assets/backend is the gap.

#69 reproduced the Ruby 2.7/ZIP mismatch and source CI’s silent dependency downgrade. It is fixed through source PR #70 and controller PR #1: declared Ruby 3.3.9, Bundler 2.4.22, Jekyll 3.10, patched rubyzip 3.4.1, frozen installation and lockfile guards. Historical saved sources retain their Ruby 2.7 restore path. PR validation has separate concurrency and cannot deploy; existing main-only Pages protection remains.

Exact runtime preview 39678798536, frozen source CI 39678613800, native production Pages 39679088864 and post-merge CI 39679089170 pass. Live production build-info confirms merge 2f7bb8a13e7f36678014d533b70ed19a4f6c54cc. This is an unversioned infrastructure delivery, not publication of the proposed Cleaner analytics release.

John delegated technical review/merge for these fixes; scoped branches, PRs, checks, staging evidence and rollback remain required. Saved staging 4fd49e45ea77bd59ed82ebb6b539e705a9b6c4de was restored in 39679563070; live build-info confirmed its exact SHA/run and the saved selection file remained unchanged. #69 is closed. Both merged maintenance branches were recoverably deleted; active feature and integration branches were preserved. The protected Worker was not deployed by this maintenance.