release: prepare v1.2.0

Author: juanklagos

CHANGELOG.md

@@ -6,6 +6,67 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ---
 
+## [v1.2.0] — 2026-03-18
+
+### Added
+- Dedicated MCP CI workflow:
+  - `.github/workflows/mcp.yml`
+- MCP integration test covering:
+  - workspace creation
+  - spec creation
+  - validation
+  - gate checks
+  - status and roadmap generation
+  - project log and resource reads
+- Public roadmap docs:
+  - `docs/en/35-public-roadmap.md`
+  - `docs/es/35-roadmap-publico.md`
+- Tested client setup recipes:
+  - `docs/en/36-client-setup-recipes.md`
+  - `docs/es/36-recetas-setup-clientes.md`
+- Versioning strategy docs:
+  - `docs/en/37-versioning-strategy.md`
+  - `docs/es/37-estrategia-versionado.md`
+- Media/public launch assets:
+  - `docs/assets/social-preview.svg`
+  - `docs/en/38-media-kit.md`
+  - `docs/es/38-kit-medios.md`
+- Next release preparation docs:
+  - `docs/en/39-v1.2.0-preparation.md`
+  - `docs/es/39-preparacion-v1.2.0.md`
+- Adoption-oriented GitHub issue templates:
+  - `bug-report`
+  - `use-case`
+- End-to-end example:
+  - `examples/002-mcp-end-to-end/`
+
+### Changed
+- Internal package versions are now aligned with the framework release:
+  - `@sdd/sdd-core` → `1.2.0`
+  - `@sdd/sdd-mcp` → `1.2.0`
+- README and docs index now surface:
+  - roadmap
+  - client setup recipes
+  - versioning strategy
+  - media kit
+  - next release prep
+- Fixed `sdd_create_spec` to create the spec directory before creating `contracts/`.
+- Repository positioning is now clearly framed as:
+  - operational SDD framework
+  - AI guidance
+  - GitHub Spec Kit reference
+  - MCP support
+
+### Verified
+- `npm run typecheck`
+- `npm run build`
+- `npm run mcp:smoke`
+- `npm run mcp:http:smoke`
+- `npm run mcp:test`
+- `./scripts/validate-sdd.sh . --strict`
+- `./scripts/check-sdd-policy.sh .`
+- `./scripts/check-sdd-gate.sh .`
+
 ## [v1.1.0] — 2026-03-18
 
 ### Added

README.es.md

@@ -8,7 +8,7 @@
   </p>
 
   <p>
-    <img src="https://img.shields.io/badge/version-v1.1.0-blue?style=for-the-badge" alt="Version">
+    <img src="https://img.shields.io/badge/version-v1.2.0-blue?style=for-the-badge" alt="Version">
     <a href="./START_HERE_NON_TECH.md"><img src="https://img.shields.io/badge/🧑‍💼_NO_TÉCNICO-Iniciar-green?style=for-the-badge" alt="Inicio no técnico"></a>
     <a href="./AI_START_HERE.md"><img src="https://img.shields.io/badge/🤖_INICIO_IA-Abrir-purple?style=for-the-badge" alt="AI Start"></a>
     <a href="./QUICKSTART.md"><img src="https://img.shields.io/badge/🚀_QUICKSTART-5_Minutos-ff6b35?style=for-the-badge" alt="Quickstart"></a>

README.md

@@ -8,7 +8,7 @@
   </p>
 
   <p>
-    <img src="https://img.shields.io/badge/version-v1.1.0-blue?style=for-the-badge" alt="Version">
+    <img src="https://img.shields.io/badge/version-v1.2.0-blue?style=for-the-badge" alt="Version">
     <a href="./START_HERE_NON_TECH.md"><img src="https://img.shields.io/badge/🧑‍💼_NON--TECH-Start-green?style=for-the-badge" alt="Non Technical Start"></a>
     <a href="./AI_START_HERE.md"><img src="https://img.shields.io/badge/🤖_AI_START-Open-purple?style=for-the-badge" alt="AI Start"></a>
     <a href="./QUICKSTART.md"><img src="https://img.shields.io/badge/🚀_QUICKSTART-5_Minutes-ff6b35?style=for-the-badge" alt="Quickstart"></a>

docs/en/34-launch-kit.md

@@ -22,25 +22,28 @@ https://github.com/juanklagos/spec-driven-development-template
 ## LinkedIn post
 
 ```text
-I just shipped v1.1.0 of my Spec-Driven Development Template.
+I just shipped v1.2.0 of my Spec-Driven Development Template.
 
-The goal is simple: reduce the friction of starting real projects with SDD and make AI assistants follow a clean, repeatable flow.
+This repository is evolving into an operational SDD framework, not just a documentation starter.
 
-New in this version:
-- real MCP server support
-- local `sdd-mcp` for operational SDD workflows
+What it now includes:
+- GitHub Spec Kit as the primary reference flow
+- multi-agent operating rules
+- runnable work isolated in ./www/<project-name>
+- local MCP server (`sdd-mcp`)
 - stdio + Streamable HTTP
-- copy-paste configs for Cursor, Claude Code, and Codex
-- active project resources for idea, specs, roadmap, status, logbook, and handoffs
+- typed SDD core
+- MCP integration tests and CI
+- copy-paste client configs for Cursor, Claude Code, and Codex
 
 Repository:
 https://github.com/juanklagos/spec-driven-development-template
 
-This is meant to help teams and solo builders move from idea -> spec -> plan -> tasks -> validation with less ambiguity and better traceability.
+The goal is to reduce friction from idea -> spec -> plan -> tasks -> validation, and make different AI assistants behave more consistently across real project work.
 ```
 
 ## Short release note
 
 ```text
-v1.1.0 adds a real MCP layer to the SDD framework: typed core logic, local MCP server, structured tool outputs, active project resources, HTTP transport, and client-ready configs.
+v1.2.0 strengthens the framework as an operational SDD system: MCP CI, integration tests, package version alignment, client setup recipes, public roadmap, media assets, and adoption examples.
 ```

docs/es/34-kit-lanzamiento.md

@@ -22,25 +22,28 @@ https://github.com/juanklagos/spec-driven-development-template
 ## Post para LinkedIn
 
 ```text
-Acabo de publicar la versión v1.1.0 de mi Spec-Driven Development Template.
+Acabo de publicar la versión v1.2.0 de mi Spec-Driven Development Template.
 
-El objetivo es simple: reducir la fricción de iniciar proyectos reales con SDD y lograr que los asistentes de IA sigan un flujo limpio y repetible.
+Este repositorio está evolucionando hacia un framework operativo de SDD, no solo un starter de documentación.
 
-Nuevo en esta versión:
-- soporte MCP real
-- `sdd-mcp` local para flujos operativos de SDD
+Ahora incluye:
+- GitHub Spec Kit como flujo de referencia principal
+- reglas operativas multi-agente
+- trabajo ejecutable aislado en ./www/<project-name>
+- servidor MCP local (`sdd-mcp`)
 - stdio + Streamable HTTP
+- core SDD tipado
+- CI y tests de integración MCP
 - configuraciones copy/paste para Cursor, Claude Code y Codex
-- resources del proyecto activo para idea, specs, roadmap, estado, bitácora y handoffs
 
 Repositorio:
 https://github.com/juanklagos/spec-driven-development-template
 
-Esto está pensado para ayudar a equipos y builders individuales a pasar de idea -> spec -> plan -> tasks -> validación con menos ambigüedad y mejor trazabilidad.
+El objetivo es reducir fricción de idea -> spec -> plan -> tasks -> validación y hacer que distintas IA trabajen de forma más consistente en proyectos reales.
 ```
 
 ## Nota corta de release
 
 ```text
-v1.1.0 agrega una capa MCP real al framework SDD: core tipado, servidor MCP local, salidas estructuradas, resources del proyecto activo, transporte HTTP y configuraciones listas para clientes.
+v1.2.0 fortalece el framework como sistema operativo de SDD: CI MCP, tests de integración, alineación de versiones internas, recetas de setup por cliente, roadmap público, assets de difusión y ejemplos de adopción.
 ```

package-lock.json

@@ -1,7 +1,7 @@
 {
   "name": "spec-driven-development-template",
   "private": true,
-  "version": "1.1.0",
+  "version": "1.2.0",
   "type": "module",
   "workspaces": [
     "packages/*"

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sdd/sdd-core",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "private": true,
   "type": "module",
   "main": "./dist/index.js",

packages/sdd-core/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sdd/sdd-mcp",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "private": true,
   "type": "module",
   "main": "./dist/index.js",
@@ -16,7 +16,7 @@
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.27.1",
-    "@sdd/sdd-core": "1.1.0",
+    "@sdd/sdd-core": "1.2.0",
     "zod": "^3.25.76"
   }
 }