docs: add v1.2.0 release notes

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: markhazleton

.documentation/releases/v1.2.0/release-notes.md

@@ -0,0 +1,45 @@
+# Release Notes: v1.2.0
+
+## Release Metadata
+
+- **Version**: v1.2.0
+- **Release Date**: 2026-03-07
+- **Previous Version**: v1.1.0
+
+## Highlights
+
+This release introduces version tracking for consumer projects. Every time a project runs `specify init` or `specify upgrade`, a `.documentation/SPECKIT_VERSION` stamp file is written with the installed version, date, and AI agent key. This gives AI commands and scripts a single, offline source of truth for the installed version — no network call required.
+
+A new `/speckit.upgrade` AI command guides agents through the full upgrade workflow: reading the version stamp, comparing to the latest release, classifying framework-owned vs. user-owned files, identifying stale paths, running the upgrade, and verifying the stamp was updated.
+
+The `/speckit.site-audit` command now includes a **Spec Kit Spark Version** check (Step 4) with structured finding codes (VER1–VER5) covering missing stamps, outdated versions, and stale pre-migration paths.
+
+## New Features
+
+### SPECKIT_VERSION stamp
+
+`specify init` and `specify upgrade` now write `.documentation/SPECKIT_VERSION` after every successful install or upgrade. The file records the installed version, install date, and agent key.
+
+### /speckit.upgrade AI command
+
+New `templates/commands/upgrade.md` — a dedicated AI agent command that reads the version stamp, compares to the latest release, classifies files as framework-owned vs. user-owned, identifies stale paths, runs `specify upgrade`, and verifies the stamp was updated after completion.
+
+### Version check in /speckit.site-audit
+
+Audit reports now include a **Spec Kit Spark Version** section (Step 4) with VER1–VER5 finding codes for missing stamps, outdated versions, and stale pre-migration paths.
+
+### Release workflow version bump step
+
+`templates/commands/release.md` now includes Step 9 — *Bump Version in Source Files* — which instructs maintainers to update `pyproject.toml`, verifies three-way consistency (pyproject / CHANGELOG / git tag), and explains that consumer projects receive the new stamp automatically on their next `specify upgrade`.
+
+### `SPECKIT_VERSION_PATH` and `INSTALLED_VERSION` in release-context scripts
+
+Both `release-context.ps1` and `release-context.sh` now surface the consumer project's installed version in JSON and human-readable output.
+
+### `read_version_stamp()` helper
+
+New Python helper in the CLI that reads and parses `.documentation/SPECKIT_VERSION` back as a dict; used in the post-upgrade summary to display the newly written version.
+
+## Upgrade Guide
+
+Run `specify upgrade` in your consumer project to receive the version stamp automatically.