cc-devflow 4.2.0 → 4.4.1

package/CHANGELOG.md

@@ -7,6 +7,103 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ---
 
+## [Unreleased]
+
+## [4.4.1] - 2026-04-25
+
+### 🔧 Canonical Change Keys + Planning Contract Hardening
+
+v4.4.1 tightens the planning and release workflow contracts so new change
+directories use explicit `REQ-*` / `FIX-*` prefixes and executable plans keep
+test-first handoffs as a native requirement.
+
+### Added
+
+- Added a public `cc-investigate` skill so bug work can follow `cc-investigate -> cc-do -> cc-check -> cc-act` instead of overloading `cc-plan`.
+- Added a distributed maintenance skill `cc-spec-init` for capability-centered spec bootstrap, capability truth maintenance, and `change-meta.json` link repair.
+- Added runtime coverage for canonical change-key generation, legacy lowercase directory compatibility, `FIX-*` ids, and rejection of stale `BUG-*` ids.
+
+### Changed
+
+- Documented the workflow as two shared-tail loops: `PDCA` for feature/scope work and `IDCA/DDCA` for root-cause work.
+- Updated public distribution, publish validation, and Codex mirror expectations so `cc-investigate` ships with the pack.
+- Updated `cc-do` and `cc-check` contracts so they can consume `ANALYSIS.md` handoffs and reroute failed bug fixes back to `cc-investigate`.
+- Updated `cc-roadmap`, `cc-plan`, `cc-investigate`, `cc-do`, `cc-check`, and `cc-act` to carry capability/spec linkage through roadmap, planning, execution, verification, and closeout.
+- Updated public docs and example bindings so `devflow/specs/` is documented as durable capability truth and `change-meta.json` is documented as durable change truth.
+- Updated `cc-plan` and `cc-investigate` so new planning outputs must use `REQ-<number>-<description>` for requirement work and `FIX-<number>-<description>` for bug-fix work.
+- Updated public examples to use uppercase `REQ-*` change directories.
+
+### Fixed
+
+- Fixed path resolution so new change directories no longer silently downcase
+  `REQ-*` ids into `req-*`.
+
+## [4.4.0] - 2026-04-10
+
+### 🚀 Review-Gated Delivery + Distribution Cleanup
+
+v4.4.0 tightens the requirement runtime contract so planning, dispatch, verify, and release operate on the same execution state, while npm distribution now ships only the public workflow surface.
+
+### Added
+
+- Added richer task manifest metadata, including phase, parallelism, acceptance, verification, evidence, review state, and execution cursor tracking.
+- Added native review aggregation in `lib/harness/review.js` so verify/release can block on missing or failed task review proof.
+- Added `.claude/skills/docs-sync/` as a maintenance skill for syncing skill versions, skill changelogs, and affected public docs before commit or ship.
+- Added `config/distributable-skills.json` so CLI/template distribution uses an explicit public-skill allowlist.
+
+### Changed
+
+- `planner`, `dispatch`, `resume`, and `query` now derive the same ready task and active phase from manifest state instead of guessing from the first pending item.
+- `verify` and release-facing outputs now emit explicit verdicts, review summaries, reroute hints, and blocking findings tied to review artifacts.
+- Documented the repository rule that changes to shipped skills must update the skill `version`, local `CHANGELOG.md`, and impacted README / CONTRIBUTING / docs content together.
+- `cc-devflow init` and npm packaging now distribute only public workflow skills; maintainer-only skills such as `docs-sync` and `npm-release` stay out of the shipped template.
+
+### Benefits
+
+- ✅ Review proof is now a first-class gate instead of tribal process
+- ✅ Requirement execution state is resumable and dependency-aware
+- ✅ Packaged output exposes a cleaner public surface for npm consumers
+
+## [4.3.0] - 2026-03-13
+
+### ✨ TDD Enforcement + OpenSpec Interop
+
+v4.3.0 adds automatic TDD order validation and bidirectional OpenSpec conversion to solve requirement drift problems.
+
+#### Added
+
+- **TDD Order Validation**
+  - Added `validateTDDOrder()` in `lib/harness/planner.js` to enforce Constitution Article VI
+  - Validates that [IMPL] tasks depend on corresponding [TEST] tasks
+  - Validates that [TEST] tasks don't depend on [IMPL] tasks
+  - Intelligent feature name matching with fuzzy algorithm (removes suffixes like "测试", "实现", "功能")
+  - Extended `TaskSchema` in `lib/harness/schemas.js` with `type` field (TEST/IMPL/OTHER)
+  - Comprehensive test coverage in `lib/harness/__tests__/planner.tdd.test.js` (10 tests, all passing)
+
+- **OpenSpec Interoperability**
+  - Added `.claude/scripts/import-openspec.js` for OpenSpec → CC-DevFlow conversion
+    - Parses OpenSpec format (Purpose + Requirements + BDD scenarios)
+    - Auto-generates TDD tasks (TEST + IMPL pairs with correct dependencies)
+    - Adds Design section with [NEEDS CLARIFICATION] markers
+    - Generates Verification checklist
+  - Added `.claude/scripts/export-openspec.js` for CC-DevFlow → OpenSpec conversion
+    - Strips YAML frontmatter and metadata
+    - Removes Design, Tasks, Verification sections
+    - Removes [NEEDS CLARIFICATION] markers
+    - Outputs pure Requirements in OpenSpec format
+  - Added `.claude/commands/flow/import-openspec.md` command documentation
+  - Added `.claude/commands/flow/export-openspec.md` command documentation
+  - Comprehensive test coverage in `.claude/scripts/__tests__/openspec.test.js` (5 tests, all passing)
+  - Round-trip conversion preserves requirements integrity
+
+#### Benefits
+
+- ✅ Automatic enforcement of TDD order (Constitution Article VI)
+- ✅ Prevents implementation before tests at parse time
+- ✅ Bidirectional OpenSpec compatibility
+- ✅ Automatic TDD task generation during import
+- ✅ Clean requirement export without implementation details
+
 ## [4.2.0] - 2026-02-19
 
 ### 🧠 Long-Running Harness Protocol Alignment
@@ -317,11 +414,11 @@ v4.1.0 introduces Claude Team functionality for multi-agent parallel development
 
 ---
 
-## [4.3.0] - 2026-02-07
+## [4.2.1] - 2026-02-07
 
 ### 🌿 Git Worktree Integration: Parallel Development Support
 
-v4.3.0 introduces Git Worktree integration for parallel development with isolated Claude Code sessions.
+v4.2.1 introduces Git Worktree integration for parallel development with isolated Claude Code sessions.
 
 #### Added
 
@@ -377,11 +474,11 @@ v4.3.0 introduces Git Worktree integration for parallel development with isolate
 
 ---
 
-## [4.1.0] - 2026-02-07
+## [4.0.1] - 2026-02-07
 
 ### 🎯 Unified Specification Phase: /flow-spec Command
 
-v4.1.0 merges flow-prd/flow-tech/flow-ui/flow-epic into a single `/flow-spec` command with parallel execution of Tech + UI agents.
+v4.0.1 merges flow-prd/flow-tech/flow-ui/flow-epic into a single `/flow-spec` command with parallel execution of Tech + UI agents.
 
 #### Added