chore: update version references to v1.6.0 in roadmap and release documentation

Author: markhazleton

.documentation/roadmap.md

@@ -18,7 +18,7 @@ Spec Kit Spark aims to become the definitive toolkit for AI-agent driven softwar
 
 ---
 
-## Current Release: v1.1.0
+## Current Release: v1.6.0
 
 ### What's Implemented
 
@@ -45,21 +45,21 @@ Spec Kit Spark aims to become the definitive toolkit for AI-agent driven softwar
 - ✅ `/speckit.quickfix` - Lightweight workflow for bug fixes
 - ✅ `/speckit.release` - Release documentation and archival
 - ✅ `/speckit.evolve-constitution` - Constitution amendment proposals
+- ✅ `/speckit.harvest` - Knowledge-preserving cleanup for stale docs and completed specs
+- ✅ `/speckit.repo-story` - Evidence-based repository narrative generation
 
 #### CLI Commands
 
 - ✅ `specify init` - Initialize new or existing projects
-- ✅ `specify upgrade` - Upgrade existing projects (NEW in v1.1.0)
+- ✅ `specify upgrade` - Upgrade existing projects
 - ✅ `specify check` - Verify tool dependencies
 - ✅ `specify version` - Show version information
 
-#### Migration & Upgrade Tools (NEW in v1.1.0)
+#### Architecture (NEW in v1.6.0)
 
-- ✅ Migration scripts (PowerShell + Bash) - Automated migration from old structure
-- ✅ Dry-run mode - Preview changes before applying
-- ✅ Cleanup mode - Remove backup directories after verification
-- ✅ Auto-detection - Detect AI assistant and migration needs
-- ✅ Safety checks - Git status checks, confirmation prompts, backups
+- ✅ Agent-agnostic canonical layout — prompts in `.documentation/commands/` with thin platform shims
+- ✅ Multi-user personalization (`/speckit.personalize`) — per-user overrides in `.documentation/{git-user}/commands/`
+- ✅ SPECKIT_VERSION stamp — version tracking for consumer projects
 
 #### Platform Support
 
@@ -71,7 +71,7 @@ Spec Kit Spark aims to become the definitive toolkit for AI-agent driven softwar
 
 ---
 
-## Near-Term Roadmap (v1.2.x)
+## Near-Term Roadmap (v1.7.x – v1.8.x)
 
 ### Enhanced Technical Debt Tracking
 
@@ -106,7 +106,7 @@ Spec Kit Spark aims to become the definitive toolkit for AI-agent driven softwar
 
 ---
 
-## Medium-Term Roadmap (v0.2.x)
+## Medium-Term Roadmap (v1.9.x – v2.x)
 
 ### Constitution Evolution Automation
 
@@ -143,7 +143,7 @@ Spec Kit Spark aims to become the definitive toolkit for AI-agent driven softwar
 
 ---
 
-## Long-Term Vision (v1.0+)
+## Long-Term Vision (v2.x+)
 
 ### Intelligent Context Management
 
@@ -245,8 +245,8 @@ Spec Kit Spark follows standard [Semantic Versioning 2.0.0](https://semver.org/)
 vMAJOR.MINOR.PATCH
 
 Examples:
-- v1.1.0  (current stable release)
-- v1.2.0  (next minor feature additions)
+- v1.6.0  (current stable release)
+- v1.7.0  (next minor feature additions)
 - v2.0.0  (breaking changes)
 ```
 
@@ -279,4 +279,4 @@ Examples:
 
 ---
 
-> Last updated: February 2026
+> Last updated: April 2026

README.md

@@ -754,21 +754,21 @@ Spec Kit Spark is actively developed with a clear vision for the future:
 - ✅ Agent-agnostic architecture with canonical prompts and thin platform shims
 - ✅ Multi-user personalization (`/speckit.personalize`)
 
-### Near-Term (v0.1.x)
+### Near-Term (v1.7.x – v1.8.x)
 
 - 🔄 Enhanced technical debt tracking with metrics storage
 - 🔄 Trend visualization for compliance scores
 - 🔄 Improved quickfix-to-spec escalation workflow
 - 🔄 Constitution template library
 
-### Medium-Term (v0.2.x)
+### Medium-Term (v1.9.x – v2.x)
 
 - 📋 CI/CD pipeline integration (GitHub Actions, Azure DevOps)
 - 📋 Business value alignment documentation
 - 📋 Cross-project governance for organizations
 - 📋 Interactive constitution builder
 
-### Long-Term (v1.0+)
+### Long-Term (v2.x+)
 
 - 🎯 Spec-to-test generation pipeline
 - 🎯 Multi-repository constitution inheritance

templates/commands/release.md

@@ -382,7 +382,33 @@ When running **Create Release** via `workflow_dispatch`, set `release_version` t
 `{NEXT_VERSION}` (or `v{NEXT_VERSION}`) so the workflow publishes the intended tag
 instead of auto-incrementing from the latest existing tag.
 
-### 10. Clean Slate Preparation
+### 10. Update Public-Facing Version References
+
+After bumping `pyproject.toml` (Step 9), update **all** public documents that mention the current release version so they stay in sync. **Skip if DRY_RUN** — but list the files that would change.
+
+#### A. Roadmap files
+
+Update **both** roadmap files to reflect the new current release:
+
+| File | Field to update |
+|------|-----------------|
+| `README.md` → `## 🗺️ Roadmap` | `### Current Release (v{NEXT_VERSION})` — add any new capabilities to the checked list |
+| `/.documentation/roadmap.md` | `## Current Release: v{NEXT_VERSION}` — move newly shipped items from Near-Term into Current, update version example |
+
+Ensure future roadmap section version ranges (`Near-Term`, `Medium-Term`, `Long-Term`) are **ahead** of `{NEXT_VERSION}`. If any future section uses a version number ≤ `{NEXT_VERSION}`, bump it forward.
+
+#### B. Release notes / index page
+
+| File | Field to update |
+|------|-----------------|
+| `release_notes.md` | Update highlights and "What's New" to `{NEXT_VERSION}` |
+| `/.documentation/index.md` | Update any version badges or "latest" references |
+
+#### C. Verify — no stale version strings
+
+Run a quick search for the **old** version string (`{CURRENT_VERSION}`) across `README.md`, `release_notes.md`, `.documentation/*.md`, and confirm every remaining reference is intentional (e.g., CHANGELOG history). Flag any stale occurrences for manual review.
+
+### 11. Clean Slate Preparation
 
 After archival (skip if DRY_RUN):
 
@@ -405,7 +431,7 @@ For each quickfix in QUICKFIXES:
 1. Create `/.documentation/specs/.gitkeep` if directory is empty
 2. Create `/.documentation/quickfixes/.gitkeep` if directory is empty
 
-### 11. Output Summary
+### 12. Output Summary
 
 #### Dry Run Output
 
@@ -471,7 +497,9 @@ To execute this release:
 
 1. Confirm `pyproject.toml` has been bumped to `{NEXT_VERSION}` (Step 9A above).
 
-2. Review generated documentation:
+2. Confirm roadmap and public docs reference `{NEXT_VERSION}` (Step 10 above).
+
+3. Review generated documentation:
    - `/.documentation/releases/v{NEXT_VERSION}/release-notes.md`
    - `CHANGELOG.md`