@programinglive/dev-workflow-mcp-server 1.5.2 → 1.5.3

package/docs/product/PRD.md

@@ -1,67 +1,67 @@
-# Product Requirements Document (PRD)
-
-## 1. Overview
-- **Product**: Development Workflow MCP Server
-- **Prepared by**: Cascade (AI assistant)
-- **Date**: 2025-10-31
-- **Status**: Draft v0.1
-
-## 2. Problem Statement
-Developers need structured guidance to maintain disciplined workflows across projects. Existing tooling lacks enforcement of sequential best practices (testing, documentation, release hygiene) and offers limited visibility into historical task execution.
-
-## 3. Goals & Objectives
-1. Enforce a consistent, auditable development workflow across teams.
-2. Provide actionable guidance for each workflow phase within IDE-integrated environments.
-3. Maintain per-project, per-user workflow state while supporting shared infrastructure (e.g., SQLite summaries, dashboard).
-
-## 4. Non-Goals
-- Replacing full-featured project management tools.
-- Implementing source control hosting or CI/CD pipelines.
-- Providing opinionated task estimation or prioritization features.
-
-## 5. Target Users & Personas
-- **Individual developers** seeking workflow discipline.
-- **Team leads** requiring enforced process compliance.
-- **Tool integrators** embedding MCP capabilities into IDEs or agents.
-
-## 6. User Stories
-1. As a developer, I want to be guided through the workflow steps so I can avoid skipping critical tasks.
-2. As a team lead, I want an auditable history of workflow completion so I can ensure compliance.
-3. As an integrator, I want a simple API (tools/prompts) so I can plug the MCP server into existing agent workflows.
-
-## 7. Functional Requirements
-- Provide MCP tools covering the full workflow lifecycle (start task, fix, test, document, commit, release, complete).
-- Persist workflow state per project and per user, with compatibility handling for legacy locations.
-- Offer aggregated project summaries (JSON artifacts, SQLite sync, optional web dashboard).
-- Guard release commands to ensure prerequisites are satisfied.
-- Support `run_full_workflow` for scripted execution of all steps with validation.
-- Web dashboard displays version dynamically from `package.json` via `/api/version` endpoint to stay in sync after releases.
-
-## 8. Technical Considerations
-- Node.js (ESM) codebase leveraging `@modelcontextprotocol/sdk`.
-- File-based state stored under `.state/users/<user>/workflow-state.json` with compatibility symlinks.
-- Optional SQLite integration for history and summary caching.
-- Vite build pipeline for distribution bundle; source usage recommended for MCP.
-- Windows compatibility requirements (Python, Build Tools for native modules).
-- **Deployment options**: Local development, Netlify (static), Plesk (full-featured).
-
-## 9. Success Metrics
-- ≥90% of workflow operations executed via MCP tools (vs. manual overrides).
-- Reduction in release guard violations to <5% of attempts.
-- Positive qualitative feedback on guidance clarity from pilot teams.
-
-## 10. Milestones
-1. **MVP**: Core workflow tools, state persistence, basic history (complete).
-2. **Enhancements**: Improved project root detection, compatibility mirrors, `run_full_workflow` automation (complete).
-3. **v1.5.0**: Netlify deployment support for static web dashboard (complete).
-4. **Future**: Expanded dashboard analytics, customizable workflows, richer integrations.
-
-## 11. Risks & Mitigations
-- **Risk**: Workflow feels overly prescriptive. **Mitigation**: Provide escape hatches (`force_complete_task`, `drop_task`) with audit trails.
-- **Risk**: State corruption due to concurrent access. **Mitigation**: File locking and defensive JSON parsing (existing code handles gracefully, but monitor).
-- **Risk**: Integration friction with IDE clients. **Mitigation**: Maintain detailed README instructions and example configurations.
-
-## 12. Open Questions
-- Should additional workflow phases (e.g., design review) be supported?
-- How should multi-branch workflows be represented in history summaries?
-- What telemetry or analytics are acceptable within privacy constraints?
+# Product Requirements Document (PRD)
+
+## 1. Overview
+- **Product**: Development Workflow MCP Server
+- **Prepared by**: Cascade (AI assistant)
+- **Date**: 2025-10-31
+- **Status**: Draft v0.1
+
+## 2. Problem Statement
+Developers need structured guidance to maintain disciplined workflows across projects. Existing tooling lacks enforcement of sequential best practices (testing, documentation, release hygiene) and offers limited visibility into historical task execution.
+
+## 3. Goals & Objectives
+1. Enforce a consistent, auditable development workflow across teams.
+2. Provide actionable guidance for each workflow phase within IDE-integrated environments.
+3. Maintain per-project, per-user workflow state while supporting shared infrastructure (e.g., SQLite summaries, dashboard).
+
+## 4. Non-Goals
+- Replacing full-featured project management tools.
+- Implementing source control hosting or CI/CD pipelines.
+- Providing opinionated task estimation or prioritization features.
+
+## 5. Target Users & Personas
+- **Individual developers** seeking workflow discipline.
+- **Team leads** requiring enforced process compliance.
+- **Tool integrators** embedding MCP capabilities into IDEs or agents.
+
+## 6. User Stories
+1. As a developer, I want to be guided through the workflow steps so I can avoid skipping critical tasks.
+2. As a team lead, I want an auditable history of workflow completion so I can ensure compliance.
+3. As an integrator, I want a simple API (tools/prompts) so I can plug the MCP server into existing agent workflows.
+
+## 7. Functional Requirements
+- Provide MCP tools covering the full workflow lifecycle (start task, fix, test, document, commit, release, complete).
+- Persist workflow state per project and per user, with compatibility handling for legacy locations.
+- Offer aggregated project summaries (JSON artifacts, SQLite sync, optional web dashboard).
+- Guard release commands to ensure prerequisites are satisfied.
+- Support `run_full_workflow` for scripted execution of all steps with validation.
+- Web dashboard displays version dynamically from `package.json` via `/api/version` endpoint to stay in sync after releases.
+
+## 8. Technical Considerations
+- Node.js (ESM) codebase leveraging `@modelcontextprotocol/sdk`.
+- File-based state stored under `.state/users/<user>/workflow-state.json` with compatibility symlinks.
+- Optional SQLite integration for history and summary caching.
+- Vite build pipeline for distribution bundle; source usage recommended for MCP.
+- Windows compatibility requirements (Python, Build Tools for native modules).
+- **Deployment options**: Local development, Netlify (static), Plesk (full-featured).
+
+## 9. Success Metrics
+- ≥90% of workflow operations executed via MCP tools (vs. manual overrides).
+- Reduction in release guard violations to <5% of attempts.
+- Positive qualitative feedback on guidance clarity from pilot teams.
+
+## 10. Milestones
+1. **MVP**: Core workflow tools, state persistence, basic history (complete).
+2. **Enhancements**: Improved project root detection, compatibility mirrors, `run_full_workflow` automation (complete).
+3. **v1.5.0**: Netlify deployment support for static web dashboard (complete).
+4. **Future**: Expanded dashboard analytics, customizable workflows, richer integrations.
+
+## 11. Risks & Mitigations
+- **Risk**: Workflow feels overly prescriptive. **Mitigation**: Provide escape hatches (`force_complete_task`, `drop_task`) with audit trails.
+- **Risk**: State corruption due to concurrent access. **Mitigation**: File locking and defensive JSON parsing (existing code handles gracefully, but monitor).
+- **Risk**: Integration friction with IDE clients. **Mitigation**: Maintain detailed README instructions and example configurations.
+
+## 12. Open Questions
+- Should additional workflow phases (e.g., design review) be supported?
+- How should multi-branch workflows be represented in history summaries?
+- What telemetry or analytics are acceptable within privacy constraints?

package/docs/release-notes/RELEASE_NOTES.md

@@ -1,226 +1,226 @@
-# Release Notes
-
-Authoritative history of user-visible changes for the Development Workflow MCP Server. Each entry highlights the improvements that shipped with the tagged version.
-
-## Unreleased
-
-## 1.5.0 — 2025-12-02
-- See CHANGELOG for details.
-
-## 1.4.11 — 2025-12-01 — 🐛 Bug Fixes
-- move vite to dependencies to ensure build works on production (62fc4c0)
-- resolve sentry permission issues (c739f8e)
-
-## 1.4.10 — 2025-12-01 — ✨ Features
-- **dashboard:** implement random data generation for analytics chart (17e2073)
-- move dompdf to require and resolve debugbar production error (e5d1cb6)
-
-## 1.4.9 — 2025-11-30 — ♻️ Refactors
-- **dashboard:** combine analytics charts and use local Chart.js (86ed3f4)
-
-## 1.4.8 — 2025-11-30 — 🐛 Bug Fixes
-- **dashboard:** improve responsive layout for admin stats cards (33d5b39)
-- **dashboard:** improve responsive layout for admin stats cards (530400d)
-
-## 1.4.7 — 2025-11-29 — ✨ Features
-- add core doc types (PRD/README/RELEASE_NOTES) and fix CI build (8ed0567)
-- update hero text and meta description to emphasize Indonesian programmer community (681547b)
-- display dynamic version in web dashboard from /api/version (69f561d)
-- add 1.4.3 release notes (8b165f7)
-- add MCP registry metadata (mcpName & server.json) (66caea1)
-- align MCP registry schema and docs (e4e732d)
-- **release:** 1.4.4 🚀 (05a968f)
-- **release:** 1.4.5 🚀 (7e823b9)
-- **release:** 1.4.6 🚀 (7e0b672)
-
-## 1.4.6 — 2025-11-27 — 🧹 Chores
-- add MCP registry metadata (mcpName & server.json) (66caea1)
-
-## 1.4.5 — 2025-11-27 — 🐛 Bug Fixes
-- display dynamic version in web dashboard from /api/version (69f561d)
-
-## 1.4.4 — 2025-11-27 — ♻️ Refactors
-- consolidate workflow state to root .state folder only (3d69a14)
-- ensure release guard uses freshest workflow state (e07eb42)
-- remove invalid turbopack experimental config from next.config.ts (af0a7ea)
-- **web:** configure next.js root to silence warnings (22ed002)
-- **web:** improve mobile layout for hero section (53b26bf)
-- add Plesk deployment guide (de35675)
-- add 1.4.3 release notes (8b165f7)
-- fix release state detection (ed5dfd1)
-- prepare for release (a6ea2d0)
-- **release:** 1.4.2 (fac8999)
-- **release:** 1.4.2 🚀 (01b0b3c)
-- **release:** 1.4.3 🚀 (04d8c3b)
-- update task list (35663dd)
-- **web:** fix next.js lockfile warning (05ffce0)
-- add core doc types (PRD/README/RELEASE_NOTES) and fix CI build (8ed0567)
-- update hero text and meta description to emphasize Indonesian programmer community (681547b)
-- update program tracks and fix fast refresh warning (aa5bc9c)
-
-## 1.4.3 — 2025-11-27 — 🧹 Chores
-- **release:** 1.4.2 (fac8999)
-- remove invalid turbopack experimental config from next.config.ts (af0a7ea)
-- add Plesk deployment guide (de35675)
-- update program tracks and fix fast refresh warning (aa5bc9c)
-
-## 1.4.2 — 2025-11-27 — 🧹 Chores
-- fix release state detection (ed5dfd1)
-- prepare for release (a6ea2d0)
-- update task list (35663dd)
-- **web:** fix next.js lockfile warning (05ffce0)
-- ensure release guard uses freshest workflow state (e07eb42)
-- **web:** configure next.js root to silence warnings (22ed002)
-- **web:** improve mobile layout for hero section (53b26bf)
-- consolidate workflow state to root .state folder only (3d69a14)
-
-## 1.4.1 — 2025-11-27 — 🐛 Bug Fixes
-- update build test to include postbuild (b1e2f48)
-- add custom server.js for Plesk (b3912cd)
-- migrate dashboard to Next.js with TypeScript and Tailwind CSS (bce1fec)
-- fix package.json scripts (fb25e98)
-- fix tsconfig and remove dist artifact (282759f)
-
-## 1.4.0 — 2025-11-26
-- See CHANGELOG for details.
-
-## 1.3.11 — 2025-11-23
-- Re-applied Plesk security fix (moved static files to `web/public/`).
-- Updated build configuration and server paths.
-
-## 1.3.10 — 2025-11-23
-- Fixed workflow state synchronization issue that caused forced releases.
-- Added `docs/WORKFLOW-BEST-PRACTICES.md`.
-
-## 1.3.9 — 2025-11-23
-- Improved documentation modal layout and readability.
-
-## 1.3.8 — 2025-11-23
-- Fixed documentation loading in production by tracking `dist/docs` in git.
-
-## 1.3.0 — 2025-11-22
-- Added comprehensive Antigravity integration documentation and examples.
-- Fixed Windows shell escaping for commit messages.
-- Fixed release scripts to support ESM projects.
-- Release guard now delegates to `@programinglive/commiter` and verifies the package is installed before running.
-
-## 1.2.7 — 2025-11-13
-- Delegated release process to `@programinglive/commiter`.
-
-## 1.2.6 — 2025-11-11
-- Exposed primary branch helper in CLI.
-- Updated documentation regarding commiter delegation.
-
-> **Notice:** Versions 1.2.2 through 1.2.5 were published briefly for packaging experiments and have been withdrawn.
-
-## 1.2.1 — 2025-11-03
-- Packaging touch-up; functionality remains identical to 1.2.0.
-
-## 1.2.0 — 2025-11-03
-- Reload the workflow state from disk for every tool call, preventing stale data when multiple clients manipulate the same project.
-
-## 1.1.18 — 2025-11-03
-- `commit_and_push` now auto-detects the primary branch (preferring `main`, then `master`) when none is supplied.
-
-## 1.1.17 — 2025-10-31
-- Release bookkeeping only; no user-facing changes.
-
-## 1.1.16 — 2025-10-31
-- Added npm provenance metadata so published packages include supply-chain attestations.
-
-## 1.1.15 — 2025-10-31
-- Documented the automated npm publish workflow and ensured CI builds include provenance before publishing.
-
-## 1.1.14 — 2025-10-31
-- Improved project-root detection for workflow state, fixing issues when the server runs from nested directories.
-
-## 1.1.13 — 2025-10-30
-- Version bump to distribute refreshed dashboard assets; no new functionality beyond 1.1.12.
-
-## 1.1.12 — 2025-10-30
-- Added a `node index.js call <tool>` CLI helper to invoke MCP tools without a client integration.
-- Refreshed the web dashboard with a docs modal, dedicated docs API endpoints, and streamlined navigation.
-
-## 1.1.11 — 2025-10-30
-- Introduced per-user workflow state stored under `.state/users/<id>/` to avoid collisions on shared repos.
-- Added a SQLite-backed project knowledge summary and the dashboard that visualizes history and trends.
-- Hardened resumable workflows by re-checking persisted summaries between steps.
-
-## 1.1.10 — 2025-10-29
-- Shipped the initial project knowledge library with a persisted JSON summary for future database integrations.
-
-## 1.1.9 — 2025-10-29
-- Made `run_full_workflow` resume intelligently from the current phase.
-- Expanded automated tests around README/exec updates and other workflow paths.
-
-## 1.1.8 — 2025-10-27
-- Documented the `DEV_WORKFLOW_STATE_FILE` override for relocating workflow state outside the repository.
-
-## 1.1.7 — 2025-10-26
-- Added prompts guiding developers to document changes immediately after tests pass.
-
-## 1.1.6 — 2025-10-26
-- Prevented `.state` from being created at filesystem roots.
-- Enforced that commits must land before any release action can run.
-
-## 1.1.5 — 2025-10-25
-- Introduced the release guard, blocking `npm run release:*` until every prerequisite tool has run.
-- Standardized per-project workflow state creation during installs.
-
-## 1.1.4 — 2025-10-25
-- Ensured the install script always targets the project root when initializing `.state`.
-
-## 1.1.3 — 2025-10-25
-- Packaged the MCP server for project-level installs with per-project workflow state isolation.
-
-## 1.1.2 — 2025-10-25
-- Version alignment release with no additional changes versus 1.1.1.
-
-## 1.1.1 — 2025-10-25
-- Added `force_complete_task`, letting teams close tasks early with an audit trail.
-
-## 1.1.0 — 2025-10-25
-- Added smart staging checks before commit, and made `continue_workflow` auto-run the next action in the commit phase.
-- Enabled clean-tree commits to utilize `commit_and_push` and `perform_release` without manual staging.
-- Clarified documentation for the commit/push step.
-
-## 1.0.11 — 2025-10-25
-- Added contextual "continue workflow" guidance describing the next recommended tool.
-- Blocked releases until commits are safely pushed.
-
-## 1.0.10 — 2025-10-24
-- Modularized the workflow server internals for maintainability.
-- Expanded automated tests around the release push flow.
-
-## 1.0.9 — 2025-10-23
-- Documented how local workflow state is managed across projects.
-
-## 1.0.8 — 2025-10-21
-- Added explicit workflows for skipping tests with justification and dropping tasks mid-flight.
-
-## 1.0.7 — 2025-10-20
-- Version alignment update; no new functionality recorded.
-
-## 1.0.6 — 2025-10-20
-- Strengthened release tests to ensure prerequisites are met before tagging.
-
-## 1.0.5 — 2025-10-20
-- Updated tests around `workflowState` persistence and validation.
-
-## 1.0.4 — 2025-10-20
-- Added an enforced release step after the ready check to ensure workflow order.
-- Improved Windows compatibility by quoting commit messages safely.
-
-## 1.0.3 — 2025-10-20
-- Added a project `.gitignore` and clarified cross-platform installation steps.
-
-## 1.0.2 — 2025-10-19
-- Hardened `run_tests` argument validation and normalized tool call arguments.
-- Expanded documentation around tool payload requirements.
-
-## 1.0.1 — 2025-10-18
-- Configured release tooling to support semantic version tagging moving forward.
-
-## 1.0.0 — 2025-10-18
-- Initial public release with the full MCP workflow (start → fix → tests → docs → commit → release → complete).
-- Launched project governance, contribution guidelines, and tooling scaffolding.
+# Release Notes
+
+Authoritative history of user-visible changes for the Development Workflow MCP Server. Each entry highlights the improvements that shipped with the tagged version.
+
+## Unreleased
+
+## 1.5.0 — 2025-12-02
+- See CHANGELOG for details.
+
+## 1.4.11 — 2025-12-01 — 🐛 Bug Fixes
+- move vite to dependencies to ensure build works on production (62fc4c0)
+- resolve sentry permission issues (c739f8e)
+
+## 1.4.10 — 2025-12-01 — ✨ Features
+- **dashboard:** implement random data generation for analytics chart (17e2073)
+- move dompdf to require and resolve debugbar production error (e5d1cb6)
+
+## 1.4.9 — 2025-11-30 — ♻️ Refactors
+- **dashboard:** combine analytics charts and use local Chart.js (86ed3f4)
+
+## 1.4.8 — 2025-11-30 — 🐛 Bug Fixes
+- **dashboard:** improve responsive layout for admin stats cards (33d5b39)
+- **dashboard:** improve responsive layout for admin stats cards (530400d)
+
+## 1.4.7 — 2025-11-29 — ✨ Features
+- add core doc types (PRD/README/RELEASE_NOTES) and fix CI build (8ed0567)
+- update hero text and meta description to emphasize Indonesian programmer community (681547b)
+- display dynamic version in web dashboard from /api/version (69f561d)
+- add 1.4.3 release notes (8b165f7)
+- add MCP registry metadata (mcpName & server.json) (66caea1)
+- align MCP registry schema and docs (e4e732d)
+- **release:** 1.4.4 🚀 (05a968f)
+- **release:** 1.4.5 🚀 (7e823b9)
+- **release:** 1.4.6 🚀 (7e0b672)
+
+## 1.4.6 — 2025-11-27 — 🧹 Chores
+- add MCP registry metadata (mcpName & server.json) (66caea1)
+
+## 1.4.5 — 2025-11-27 — 🐛 Bug Fixes
+- display dynamic version in web dashboard from /api/version (69f561d)
+
+## 1.4.4 — 2025-11-27 — ♻️ Refactors
+- consolidate workflow state to root .state folder only (3d69a14)
+- ensure release guard uses freshest workflow state (e07eb42)
+- remove invalid turbopack experimental config from next.config.ts (af0a7ea)
+- **web:** configure next.js root to silence warnings (22ed002)
+- **web:** improve mobile layout for hero section (53b26bf)
+- add Plesk deployment guide (de35675)
+- add 1.4.3 release notes (8b165f7)
+- fix release state detection (ed5dfd1)
+- prepare for release (a6ea2d0)
+- **release:** 1.4.2 (fac8999)
+- **release:** 1.4.2 🚀 (01b0b3c)
+- **release:** 1.4.3 🚀 (04d8c3b)
+- update task list (35663dd)
+- **web:** fix next.js lockfile warning (05ffce0)
+- add core doc types (PRD/README/RELEASE_NOTES) and fix CI build (8ed0567)
+- update hero text and meta description to emphasize Indonesian programmer community (681547b)
+- update program tracks and fix fast refresh warning (aa5bc9c)
+
+## 1.4.3 — 2025-11-27 — 🧹 Chores
+- **release:** 1.4.2 (fac8999)
+- remove invalid turbopack experimental config from next.config.ts (af0a7ea)
+- add Plesk deployment guide (de35675)
+- update program tracks and fix fast refresh warning (aa5bc9c)
+
+## 1.4.2 — 2025-11-27 — 🧹 Chores
+- fix release state detection (ed5dfd1)
+- prepare for release (a6ea2d0)
+- update task list (35663dd)
+- **web:** fix next.js lockfile warning (05ffce0)
+- ensure release guard uses freshest workflow state (e07eb42)
+- **web:** configure next.js root to silence warnings (22ed002)
+- **web:** improve mobile layout for hero section (53b26bf)
+- consolidate workflow state to root .state folder only (3d69a14)
+
+## 1.4.1 — 2025-11-27 — 🐛 Bug Fixes
+- update build test to include postbuild (b1e2f48)
+- add custom server.js for Plesk (b3912cd)
+- migrate dashboard to Next.js with TypeScript and Tailwind CSS (bce1fec)
+- fix package.json scripts (fb25e98)
+- fix tsconfig and remove dist artifact (282759f)
+
+## 1.4.0 — 2025-11-26
+- See CHANGELOG for details.
+
+## 1.3.11 — 2025-11-23
+- Re-applied Plesk security fix (moved static files to `web/public/`).
+- Updated build configuration and server paths.
+
+## 1.3.10 — 2025-11-23
+- Fixed workflow state synchronization issue that caused forced releases.
+- Added `docs/WORKFLOW-BEST-PRACTICES.md`.
+
+## 1.3.9 — 2025-11-23
+- Improved documentation modal layout and readability.
+
+## 1.3.8 — 2025-11-23
+- Fixed documentation loading in production by tracking `dist/docs` in git.
+
+## 1.3.0 — 2025-11-22
+- Added comprehensive Antigravity integration documentation and examples.
+- Fixed Windows shell escaping for commit messages.
+- Fixed release scripts to support ESM projects.
+- Release guard now delegates to `@programinglive/commiter` and verifies the package is installed before running.
+
+## 1.2.7 — 2025-11-13
+- Delegated release process to `@programinglive/commiter`.
+
+## 1.2.6 — 2025-11-11
+- Exposed primary branch helper in CLI.
+- Updated documentation regarding commiter delegation.
+
+> **Notice:** Versions 1.2.2 through 1.2.5 were published briefly for packaging experiments and have been withdrawn.
+
+## 1.2.1 — 2025-11-03
+- Packaging touch-up; functionality remains identical to 1.2.0.
+
+## 1.2.0 — 2025-11-03
+- Reload the workflow state from disk for every tool call, preventing stale data when multiple clients manipulate the same project.
+
+## 1.1.18 — 2025-11-03
+- `commit_and_push` now auto-detects the primary branch (preferring `main`, then `master`) when none is supplied.
+
+## 1.1.17 — 2025-10-31
+- Release bookkeeping only; no user-facing changes.
+
+## 1.1.16 — 2025-10-31
+- Added npm provenance metadata so published packages include supply-chain attestations.
+
+## 1.1.15 — 2025-10-31
+- Documented the automated npm publish workflow and ensured CI builds include provenance before publishing.
+
+## 1.1.14 — 2025-10-31
+- Improved project-root detection for workflow state, fixing issues when the server runs from nested directories.
+
+## 1.1.13 — 2025-10-30
+- Version bump to distribute refreshed dashboard assets; no new functionality beyond 1.1.12.
+
+## 1.1.12 — 2025-10-30
+- Added a `node index.js call <tool>` CLI helper to invoke MCP tools without a client integration.
+- Refreshed the web dashboard with a docs modal, dedicated docs API endpoints, and streamlined navigation.
+
+## 1.1.11 — 2025-10-30
+- Introduced per-user workflow state stored under `.state/users/<id>/` to avoid collisions on shared repos.
+- Added a SQLite-backed project knowledge summary and the dashboard that visualizes history and trends.
+- Hardened resumable workflows by re-checking persisted summaries between steps.
+
+## 1.1.10 — 2025-10-29
+- Shipped the initial project knowledge library with a persisted JSON summary for future database integrations.
+
+## 1.1.9 — 2025-10-29
+- Made `run_full_workflow` resume intelligently from the current phase.
+- Expanded automated tests around README/exec updates and other workflow paths.
+
+## 1.1.8 — 2025-10-27
+- Documented the `DEV_WORKFLOW_STATE_FILE` override for relocating workflow state outside the repository.
+
+## 1.1.7 — 2025-10-26
+- Added prompts guiding developers to document changes immediately after tests pass.
+
+## 1.1.6 — 2025-10-26
+- Prevented `.state` from being created at filesystem roots.
+- Enforced that commits must land before any release action can run.
+
+## 1.1.5 — 2025-10-25
+- Introduced the release guard, blocking `npm run release:*` until every prerequisite tool has run.
+- Standardized per-project workflow state creation during installs.
+
+## 1.1.4 — 2025-10-25
+- Ensured the install script always targets the project root when initializing `.state`.
+
+## 1.1.3 — 2025-10-25
+- Packaged the MCP server for project-level installs with per-project workflow state isolation.
+
+## 1.1.2 — 2025-10-25
+- Version alignment release with no additional changes versus 1.1.1.
+
+## 1.1.1 — 2025-10-25
+- Added `force_complete_task`, letting teams close tasks early with an audit trail.
+
+## 1.1.0 — 2025-10-25
+- Added smart staging checks before commit, and made `continue_workflow` auto-run the next action in the commit phase.
+- Enabled clean-tree commits to utilize `commit_and_push` and `perform_release` without manual staging.
+- Clarified documentation for the commit/push step.
+
+## 1.0.11 — 2025-10-25
+- Added contextual "continue workflow" guidance describing the next recommended tool.
+- Blocked releases until commits are safely pushed.
+
+## 1.0.10 — 2025-10-24
+- Modularized the workflow server internals for maintainability.
+- Expanded automated tests around the release push flow.
+
+## 1.0.9 — 2025-10-23
+- Documented how local workflow state is managed across projects.
+
+## 1.0.8 — 2025-10-21
+- Added explicit workflows for skipping tests with justification and dropping tasks mid-flight.
+
+## 1.0.7 — 2025-10-20
+- Version alignment update; no new functionality recorded.
+
+## 1.0.6 — 2025-10-20
+- Strengthened release tests to ensure prerequisites are met before tagging.
+
+## 1.0.5 — 2025-10-20
+- Updated tests around `workflowState` persistence and validation.
+
+## 1.0.4 — 2025-10-20
+- Added an enforced release step after the ready check to ensure workflow order.
+- Improved Windows compatibility by quoting commit messages safely.
+
+## 1.0.3 — 2025-10-20
+- Added a project `.gitignore` and clarified cross-platform installation steps.
+
+## 1.0.2 — 2025-10-19
+- Hardened `run_tests` argument validation and normalized tool call arguments.
+- Expanded documentation around tool payload requirements.
+
+## 1.0.1 — 2025-10-18
+- Configured release tooling to support semantic version tagging moving forward.
+
+## 1.0.0 — 2025-10-18
+- Initial public release with the full MCP workflow (start → fix → tests → docs → commit → release → complete).
+- Launched project governance, contribution guidelines, and tooling scaffolding.