@programinglive/dev-workflow-mcp-server 1.5.2 → 1.5.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.agent/workflows/dev-workflow-bugfix.md +250 -250
- package/.agent/workflows/dev-workflow-feature.md +201 -201
- package/.agent/workflows/dev-workflow-full-cycle.md +400 -400
- package/.agent/workflows/dev-workflow-refactor.md +238 -238
- package/.github/ISSUE_TEMPLATE/bug_report.md +34 -34
- package/.github/ISSUE_TEMPLATE/feature_request.md +25 -25
- package/.github/pull_request_template.md +22 -22
- package/.github/workflows/github-release.yml +56 -0
- package/.github/workflows/npm-publish.yml +50 -50
- package/.husky/commit-msg +0 -0
- package/CHANGELOG.md +759 -741
- package/CODE_OF_CONDUCT.md +79 -79
- package/CONTRIBUTING.md +60 -60
- package/LICENSE +21 -21
- package/README.md +632 -632
- package/SECURITY.md +20 -20
- package/db/index.js +204 -204
- package/docs/NETLIFY_DEPLOYMENT.md +125 -125
- package/docs/PLESK_DEPLOYMENT.md +170 -170
- package/docs/WORKFLOW-BEST-PRACTICES.md +58 -58
- package/docs/antigravity/EXAMPLES.md +535 -535
- package/docs/antigravity/GETTING-STARTED.md +292 -292
- package/docs/antigravity/TROUBLESHOOTING.md +742 -742
- package/docs/antigravity/WALKTHROUGH.md +25 -25
- package/docs/antigravity/WORKFLOW-TEMPLATES.md +670 -670
- package/docs/product/PRD.md +67 -67
- package/docs/release-notes/RELEASE_NOTES.md +233 -226
- package/docs/web-dashboard.md +175 -175
- package/exec.js +49 -49
- package/index.js +279 -279
- package/install.js +73 -73
- package/package.json +4 -4
- package/release-wrapper.js +192 -192
- package/scripts/build-docs.js +63 -63
- package/scripts/extract-release-notes.cjs +78 -0
- package/scripts/hello-world.js +1 -1
- package/scripts/release.cjs +252 -252
- package/scripts/release.js +252 -0
- package/scripts/update-release-notes.cjs +178 -178
- package/scripts/update-release-notes.js +182 -0
- package/server.json +23 -23
- package/tailwind.config.js +8 -8
- package/tests/build.test.js +83 -83
- package/tests/exec.test.js +35 -35
- package/tests/handlers.test.js +1058 -1058
- package/tests/hello-world.test.js +13 -13
- package/tests/mcpRegistry.test.js +65 -65
- package/tests/patch-release.test.js +7 -0
- package/tests/release-wrapper.test.js +107 -107
- package/tests/workflowState.test.js +505 -505
- package/tools/definitions.js +332 -332
- package/tools/handlers.js +1019 -1019
- package/vite.config.js +43 -43
- package/vite.web.config.js +23 -23
- package/web/README.md +36 -36
- package/web/app/docs/page.tsx +202 -202
- package/web/app/globals.css +90 -90
- package/web/app/layout.tsx +36 -36
- package/web/app/page.tsx +15 -15
- package/web/components/ApiReference.tsx +20 -20
- package/web/components/Features.tsx +61 -61
- package/web/components/Footer.tsx +9 -9
- package/web/components/Hero.tsx +96 -96
- package/web/components/History.tsx +143 -143
- package/web/components/Navbar.tsx +64 -64
- package/web/components/Terminal.tsx +114 -114
- package/web/eslint.config.mjs +18 -18
- package/web/lib/db.js +131 -131
- package/web/lib/docs.js +73 -73
- package/web/netlify.toml +3 -3
- package/web/next.config.ts +12 -12
- package/web/package-lock.json +6560 -6560
- package/web/package.json +28 -28
- package/web/postcss.config.mjs +9 -9
- package/web/server.js +31 -31
- package/web/tailwind.config.ts +19 -19
- package/web/tsconfig.json +42 -42
- package/workflow-state.js +612 -612
package/docs/product/PRD.md
CHANGED
|
@@ -1,67 +1,67 @@
|
|
|
1
|
-
# Product Requirements Document (PRD)
|
|
2
|
-
|
|
3
|
-
## 1. Overview
|
|
4
|
-
- **Product**: Development Workflow MCP Server
|
|
5
|
-
- **Prepared by**: Cascade (AI assistant)
|
|
6
|
-
- **Date**: 2025-10-31
|
|
7
|
-
- **Status**: Draft v0.1
|
|
8
|
-
|
|
9
|
-
## 2. Problem Statement
|
|
10
|
-
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.
|
|
11
|
-
|
|
12
|
-
## 3. Goals & Objectives
|
|
13
|
-
1. Enforce a consistent, auditable development workflow across teams.
|
|
14
|
-
2. Provide actionable guidance for each workflow phase within IDE-integrated environments.
|
|
15
|
-
3. Maintain per-project, per-user workflow state while supporting shared infrastructure (e.g., SQLite summaries, dashboard).
|
|
16
|
-
|
|
17
|
-
## 4. Non-Goals
|
|
18
|
-
- Replacing full-featured project management tools.
|
|
19
|
-
- Implementing source control hosting or CI/CD pipelines.
|
|
20
|
-
- Providing opinionated task estimation or prioritization features.
|
|
21
|
-
|
|
22
|
-
## 5. Target Users & Personas
|
|
23
|
-
- **Individual developers** seeking workflow discipline.
|
|
24
|
-
- **Team leads** requiring enforced process compliance.
|
|
25
|
-
- **Tool integrators** embedding MCP capabilities into IDEs or agents.
|
|
26
|
-
|
|
27
|
-
## 6. User Stories
|
|
28
|
-
1. As a developer, I want to be guided through the workflow steps so I can avoid skipping critical tasks.
|
|
29
|
-
2. As a team lead, I want an auditable history of workflow completion so I can ensure compliance.
|
|
30
|
-
3. As an integrator, I want a simple API (tools/prompts) so I can plug the MCP server into existing agent workflows.
|
|
31
|
-
|
|
32
|
-
## 7. Functional Requirements
|
|
33
|
-
- Provide MCP tools covering the full workflow lifecycle (start task, fix, test, document, commit, release, complete).
|
|
34
|
-
- Persist workflow state per project and per user, with compatibility handling for legacy locations.
|
|
35
|
-
- Offer aggregated project summaries (JSON artifacts, SQLite sync, optional web dashboard).
|
|
36
|
-
- Guard release commands to ensure prerequisites are satisfied.
|
|
37
|
-
- Support `run_full_workflow` for scripted execution of all steps with validation.
|
|
38
|
-
- Web dashboard displays version dynamically from `package.json` via `/api/version` endpoint to stay in sync after releases.
|
|
39
|
-
|
|
40
|
-
## 8. Technical Considerations
|
|
41
|
-
- Node.js (ESM) codebase leveraging `@modelcontextprotocol/sdk`.
|
|
42
|
-
- File-based state stored under `.state/users/<user>/workflow-state.json` with compatibility symlinks.
|
|
43
|
-
- Optional SQLite integration for history and summary caching.
|
|
44
|
-
- Vite build pipeline for distribution bundle; source usage recommended for MCP.
|
|
45
|
-
- Windows compatibility requirements (Python, Build Tools for native modules).
|
|
46
|
-
- **Deployment options**: Local development, Netlify (static), Plesk (full-featured).
|
|
47
|
-
|
|
48
|
-
## 9. Success Metrics
|
|
49
|
-
- ≥90% of workflow operations executed via MCP tools (vs. manual overrides).
|
|
50
|
-
- Reduction in release guard violations to <5% of attempts.
|
|
51
|
-
- Positive qualitative feedback on guidance clarity from pilot teams.
|
|
52
|
-
|
|
53
|
-
## 10. Milestones
|
|
54
|
-
1. **MVP**: Core workflow tools, state persistence, basic history (complete).
|
|
55
|
-
2. **Enhancements**: Improved project root detection, compatibility mirrors, `run_full_workflow` automation (complete).
|
|
56
|
-
3. **v1.5.0**: Netlify deployment support for static web dashboard (complete).
|
|
57
|
-
4. **Future**: Expanded dashboard analytics, customizable workflows, richer integrations.
|
|
58
|
-
|
|
59
|
-
## 11. Risks & Mitigations
|
|
60
|
-
- **Risk**: Workflow feels overly prescriptive. **Mitigation**: Provide escape hatches (`force_complete_task`, `drop_task`) with audit trails.
|
|
61
|
-
- **Risk**: State corruption due to concurrent access. **Mitigation**: File locking and defensive JSON parsing (existing code handles gracefully, but monitor).
|
|
62
|
-
- **Risk**: Integration friction with IDE clients. **Mitigation**: Maintain detailed README instructions and example configurations.
|
|
63
|
-
|
|
64
|
-
## 12. Open Questions
|
|
65
|
-
- Should additional workflow phases (e.g., design review) be supported?
|
|
66
|
-
- How should multi-branch workflows be represented in history summaries?
|
|
67
|
-
- What telemetry or analytics are acceptable within privacy constraints?
|
|
1
|
+
# Product Requirements Document (PRD)
|
|
2
|
+
|
|
3
|
+
## 1. Overview
|
|
4
|
+
- **Product**: Development Workflow MCP Server
|
|
5
|
+
- **Prepared by**: Cascade (AI assistant)
|
|
6
|
+
- **Date**: 2025-10-31
|
|
7
|
+
- **Status**: Draft v0.1
|
|
8
|
+
|
|
9
|
+
## 2. Problem Statement
|
|
10
|
+
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.
|
|
11
|
+
|
|
12
|
+
## 3. Goals & Objectives
|
|
13
|
+
1. Enforce a consistent, auditable development workflow across teams.
|
|
14
|
+
2. Provide actionable guidance for each workflow phase within IDE-integrated environments.
|
|
15
|
+
3. Maintain per-project, per-user workflow state while supporting shared infrastructure (e.g., SQLite summaries, dashboard).
|
|
16
|
+
|
|
17
|
+
## 4. Non-Goals
|
|
18
|
+
- Replacing full-featured project management tools.
|
|
19
|
+
- Implementing source control hosting or CI/CD pipelines.
|
|
20
|
+
- Providing opinionated task estimation or prioritization features.
|
|
21
|
+
|
|
22
|
+
## 5. Target Users & Personas
|
|
23
|
+
- **Individual developers** seeking workflow discipline.
|
|
24
|
+
- **Team leads** requiring enforced process compliance.
|
|
25
|
+
- **Tool integrators** embedding MCP capabilities into IDEs or agents.
|
|
26
|
+
|
|
27
|
+
## 6. User Stories
|
|
28
|
+
1. As a developer, I want to be guided through the workflow steps so I can avoid skipping critical tasks.
|
|
29
|
+
2. As a team lead, I want an auditable history of workflow completion so I can ensure compliance.
|
|
30
|
+
3. As an integrator, I want a simple API (tools/prompts) so I can plug the MCP server into existing agent workflows.
|
|
31
|
+
|
|
32
|
+
## 7. Functional Requirements
|
|
33
|
+
- Provide MCP tools covering the full workflow lifecycle (start task, fix, test, document, commit, release, complete).
|
|
34
|
+
- Persist workflow state per project and per user, with compatibility handling for legacy locations.
|
|
35
|
+
- Offer aggregated project summaries (JSON artifacts, SQLite sync, optional web dashboard).
|
|
36
|
+
- Guard release commands to ensure prerequisites are satisfied.
|
|
37
|
+
- Support `run_full_workflow` for scripted execution of all steps with validation.
|
|
38
|
+
- Web dashboard displays version dynamically from `package.json` via `/api/version` endpoint to stay in sync after releases.
|
|
39
|
+
|
|
40
|
+
## 8. Technical Considerations
|
|
41
|
+
- Node.js (ESM) codebase leveraging `@modelcontextprotocol/sdk`.
|
|
42
|
+
- File-based state stored under `.state/users/<user>/workflow-state.json` with compatibility symlinks.
|
|
43
|
+
- Optional SQLite integration for history and summary caching.
|
|
44
|
+
- Vite build pipeline for distribution bundle; source usage recommended for MCP.
|
|
45
|
+
- Windows compatibility requirements (Python, Build Tools for native modules).
|
|
46
|
+
- **Deployment options**: Local development, Netlify (static), Plesk (full-featured).
|
|
47
|
+
|
|
48
|
+
## 9. Success Metrics
|
|
49
|
+
- ≥90% of workflow operations executed via MCP tools (vs. manual overrides).
|
|
50
|
+
- Reduction in release guard violations to <5% of attempts.
|
|
51
|
+
- Positive qualitative feedback on guidance clarity from pilot teams.
|
|
52
|
+
|
|
53
|
+
## 10. Milestones
|
|
54
|
+
1. **MVP**: Core workflow tools, state persistence, basic history (complete).
|
|
55
|
+
2. **Enhancements**: Improved project root detection, compatibility mirrors, `run_full_workflow` automation (complete).
|
|
56
|
+
3. **v1.5.0**: Netlify deployment support for static web dashboard (complete).
|
|
57
|
+
4. **Future**: Expanded dashboard analytics, customizable workflows, richer integrations.
|
|
58
|
+
|
|
59
|
+
## 11. Risks & Mitigations
|
|
60
|
+
- **Risk**: Workflow feels overly prescriptive. **Mitigation**: Provide escape hatches (`force_complete_task`, `drop_task`) with audit trails.
|
|
61
|
+
- **Risk**: State corruption due to concurrent access. **Mitigation**: File locking and defensive JSON parsing (existing code handles gracefully, but monitor).
|
|
62
|
+
- **Risk**: Integration friction with IDE clients. **Mitigation**: Maintain detailed README instructions and example configurations.
|
|
63
|
+
|
|
64
|
+
## 12. Open Questions
|
|
65
|
+
- Should additional workflow phases (e.g., design review) be supported?
|
|
66
|
+
- How should multi-branch workflows be represented in history summaries?
|
|
67
|
+
- What telemetry or analytics are acceptable within privacy constraints?
|
|
@@ -1,226 +1,233 @@
|
|
|
1
|
-
# Release Notes
|
|
2
|
-
|
|
3
|
-
Authoritative history of user-visible changes for the Development Workflow MCP Server. Each entry highlights the improvements that shipped with the tagged version.
|
|
4
|
-
|
|
5
|
-
## Unreleased
|
|
6
|
-
|
|
7
|
-
## 1.5.
|
|
8
|
-
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
-
|
|
12
|
-
-
|
|
13
|
-
|
|
14
|
-
## 1.
|
|
15
|
-
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
-
|
|
20
|
-
|
|
21
|
-
## 1.4.
|
|
22
|
-
- **dashboard:**
|
|
23
|
-
-
|
|
24
|
-
|
|
25
|
-
## 1.4.
|
|
26
|
-
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
-
|
|
30
|
-
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
-
|
|
34
|
-
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
- add MCP registry metadata (mcpName & server.json) (66caea1)
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
-
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
-
|
|
51
|
-
-
|
|
52
|
-
-
|
|
53
|
-
- **
|
|
54
|
-
- **
|
|
55
|
-
-
|
|
56
|
-
-
|
|
57
|
-
-
|
|
58
|
-
-
|
|
59
|
-
-
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
-
|
|
63
|
-
-
|
|
64
|
-
- add
|
|
65
|
-
- update
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
|
|
69
|
-
-
|
|
70
|
-
-
|
|
71
|
-
-
|
|
72
|
-
-
|
|
73
|
-
|
|
74
|
-
|
|
75
|
-
-
|
|
76
|
-
|
|
77
|
-
|
|
78
|
-
-
|
|
79
|
-
-
|
|
80
|
-
-
|
|
81
|
-
-
|
|
82
|
-
-
|
|
83
|
-
|
|
84
|
-
## 1.4.
|
|
85
|
-
-
|
|
86
|
-
|
|
87
|
-
|
|
88
|
-
-
|
|
89
|
-
-
|
|
90
|
-
|
|
91
|
-
## 1.
|
|
92
|
-
-
|
|
93
|
-
|
|
94
|
-
|
|
95
|
-
|
|
96
|
-
-
|
|
97
|
-
|
|
98
|
-
## 1.3.
|
|
99
|
-
- Fixed
|
|
100
|
-
|
|
101
|
-
|
|
102
|
-
|
|
103
|
-
-
|
|
104
|
-
|
|
105
|
-
|
|
106
|
-
|
|
107
|
-
|
|
108
|
-
|
|
109
|
-
|
|
110
|
-
|
|
111
|
-
-
|
|
112
|
-
-
|
|
113
|
-
|
|
114
|
-
|
|
115
|
-
|
|
116
|
-
|
|
117
|
-
|
|
118
|
-
|
|
119
|
-
|
|
120
|
-
|
|
121
|
-
|
|
122
|
-
|
|
123
|
-
|
|
124
|
-
|
|
125
|
-
|
|
126
|
-
|
|
127
|
-
|
|
128
|
-
|
|
129
|
-
|
|
130
|
-
|
|
131
|
-
|
|
132
|
-
|
|
133
|
-
|
|
134
|
-
|
|
135
|
-
|
|
136
|
-
|
|
137
|
-
|
|
138
|
-
|
|
139
|
-
|
|
140
|
-
|
|
141
|
-
|
|
142
|
-
-
|
|
143
|
-
|
|
144
|
-
## 1.1.
|
|
145
|
-
-
|
|
146
|
-
|
|
147
|
-
|
|
148
|
-
|
|
149
|
-
|
|
150
|
-
|
|
151
|
-
|
|
152
|
-
|
|
153
|
-
-
|
|
154
|
-
-
|
|
155
|
-
|
|
156
|
-
## 1.1.
|
|
157
|
-
-
|
|
158
|
-
|
|
159
|
-
## 1.1.
|
|
160
|
-
-
|
|
161
|
-
|
|
162
|
-
|
|
163
|
-
|
|
164
|
-
-
|
|
165
|
-
|
|
166
|
-
## 1.1.
|
|
167
|
-
-
|
|
168
|
-
|
|
169
|
-
|
|
170
|
-
|
|
171
|
-
-
|
|
172
|
-
|
|
173
|
-
## 1.1.
|
|
174
|
-
-
|
|
175
|
-
|
|
176
|
-
|
|
177
|
-
|
|
178
|
-
|
|
179
|
-
|
|
180
|
-
|
|
181
|
-
|
|
182
|
-
|
|
183
|
-
|
|
184
|
-
-
|
|
185
|
-
|
|
186
|
-
|
|
187
|
-
|
|
188
|
-
|
|
189
|
-
|
|
190
|
-
|
|
191
|
-
|
|
192
|
-
-
|
|
193
|
-
|
|
194
|
-
|
|
195
|
-
|
|
196
|
-
-
|
|
197
|
-
|
|
198
|
-
## 1.0.
|
|
199
|
-
-
|
|
200
|
-
|
|
201
|
-
|
|
202
|
-
|
|
203
|
-
|
|
204
|
-
|
|
205
|
-
|
|
206
|
-
|
|
207
|
-
|
|
208
|
-
|
|
209
|
-
|
|
210
|
-
|
|
211
|
-
|
|
212
|
-
-
|
|
213
|
-
|
|
214
|
-
## 1.0.
|
|
215
|
-
-
|
|
216
|
-
|
|
217
|
-
## 1.0.
|
|
218
|
-
-
|
|
219
|
-
-
|
|
220
|
-
|
|
221
|
-
## 1.0.
|
|
222
|
-
-
|
|
223
|
-
|
|
224
|
-
## 1.0.
|
|
225
|
-
-
|
|
226
|
-
-
|
|
1
|
+
# Release Notes
|
|
2
|
+
|
|
3
|
+
Authoritative history of user-visible changes for the Development Workflow MCP Server. Each entry highlights the improvements that shipped with the tagged version.
|
|
4
|
+
|
|
5
|
+
## Unreleased
|
|
6
|
+
|
|
7
|
+
## 1.5.3 — 2025-12-05 — 🐛 Bug Fixes
|
|
8
|
+
- correct package.json version from null to 1.5.2 for npm publish (be60c99)
|
|
9
|
+
- **news:** improve error handling and form accessibility (5e0a1a8)
|
|
10
|
+
- switch to static export for Netlify deployment (acddfd7)
|
|
11
|
+
- **release:** null 🚀 (55d7f99)
|
|
12
|
+
- **release:** prepare patch release 1.5.3 (5b92c42)
|
|
13
|
+
|
|
14
|
+
## 1.5.0 — 2025-12-02
|
|
15
|
+
- See CHANGELOG for details.
|
|
16
|
+
|
|
17
|
+
## 1.4.11 — 2025-12-01 — 🐛 Bug Fixes
|
|
18
|
+
- move vite to dependencies to ensure build works on production (62fc4c0)
|
|
19
|
+
- resolve sentry permission issues (c739f8e)
|
|
20
|
+
|
|
21
|
+
## 1.4.10 — 2025-12-01 — ✨ Features
|
|
22
|
+
- **dashboard:** implement random data generation for analytics chart (17e2073)
|
|
23
|
+
- move dompdf to require and resolve debugbar production error (e5d1cb6)
|
|
24
|
+
|
|
25
|
+
## 1.4.9 — 2025-11-30 — ♻️ Refactors
|
|
26
|
+
- **dashboard:** combine analytics charts and use local Chart.js (86ed3f4)
|
|
27
|
+
|
|
28
|
+
## 1.4.8 — 2025-11-30 — 🐛 Bug Fixes
|
|
29
|
+
- **dashboard:** improve responsive layout for admin stats cards (33d5b39)
|
|
30
|
+
- **dashboard:** improve responsive layout for admin stats cards (530400d)
|
|
31
|
+
|
|
32
|
+
## 1.4.7 — 2025-11-29 — ✨ Features
|
|
33
|
+
- add core doc types (PRD/README/RELEASE_NOTES) and fix CI build (8ed0567)
|
|
34
|
+
- update hero text and meta description to emphasize Indonesian programmer community (681547b)
|
|
35
|
+
- display dynamic version in web dashboard from /api/version (69f561d)
|
|
36
|
+
- add 1.4.3 release notes (8b165f7)
|
|
37
|
+
- add MCP registry metadata (mcpName & server.json) (66caea1)
|
|
38
|
+
- align MCP registry schema and docs (e4e732d)
|
|
39
|
+
- **release:** 1.4.4 🚀 (05a968f)
|
|
40
|
+
- **release:** 1.4.5 🚀 (7e823b9)
|
|
41
|
+
- **release:** 1.4.6 🚀 (7e0b672)
|
|
42
|
+
|
|
43
|
+
## 1.4.6 — 2025-11-27 — 🧹 Chores
|
|
44
|
+
- add MCP registry metadata (mcpName & server.json) (66caea1)
|
|
45
|
+
|
|
46
|
+
## 1.4.5 — 2025-11-27 — 🐛 Bug Fixes
|
|
47
|
+
- display dynamic version in web dashboard from /api/version (69f561d)
|
|
48
|
+
|
|
49
|
+
## 1.4.4 — 2025-11-27 — ♻️ Refactors
|
|
50
|
+
- consolidate workflow state to root .state folder only (3d69a14)
|
|
51
|
+
- ensure release guard uses freshest workflow state (e07eb42)
|
|
52
|
+
- remove invalid turbopack experimental config from next.config.ts (af0a7ea)
|
|
53
|
+
- **web:** configure next.js root to silence warnings (22ed002)
|
|
54
|
+
- **web:** improve mobile layout for hero section (53b26bf)
|
|
55
|
+
- add Plesk deployment guide (de35675)
|
|
56
|
+
- add 1.4.3 release notes (8b165f7)
|
|
57
|
+
- fix release state detection (ed5dfd1)
|
|
58
|
+
- prepare for release (a6ea2d0)
|
|
59
|
+
- **release:** 1.4.2 (fac8999)
|
|
60
|
+
- **release:** 1.4.2 🚀 (01b0b3c)
|
|
61
|
+
- **release:** 1.4.3 🚀 (04d8c3b)
|
|
62
|
+
- update task list (35663dd)
|
|
63
|
+
- **web:** fix next.js lockfile warning (05ffce0)
|
|
64
|
+
- add core doc types (PRD/README/RELEASE_NOTES) and fix CI build (8ed0567)
|
|
65
|
+
- update hero text and meta description to emphasize Indonesian programmer community (681547b)
|
|
66
|
+
- update program tracks and fix fast refresh warning (aa5bc9c)
|
|
67
|
+
|
|
68
|
+
## 1.4.3 — 2025-11-27 — 🧹 Chores
|
|
69
|
+
- **release:** 1.4.2 (fac8999)
|
|
70
|
+
- remove invalid turbopack experimental config from next.config.ts (af0a7ea)
|
|
71
|
+
- add Plesk deployment guide (de35675)
|
|
72
|
+
- update program tracks and fix fast refresh warning (aa5bc9c)
|
|
73
|
+
|
|
74
|
+
## 1.4.2 — 2025-11-27 — 🧹 Chores
|
|
75
|
+
- fix release state detection (ed5dfd1)
|
|
76
|
+
- prepare for release (a6ea2d0)
|
|
77
|
+
- update task list (35663dd)
|
|
78
|
+
- **web:** fix next.js lockfile warning (05ffce0)
|
|
79
|
+
- ensure release guard uses freshest workflow state (e07eb42)
|
|
80
|
+
- **web:** configure next.js root to silence warnings (22ed002)
|
|
81
|
+
- **web:** improve mobile layout for hero section (53b26bf)
|
|
82
|
+
- consolidate workflow state to root .state folder only (3d69a14)
|
|
83
|
+
|
|
84
|
+
## 1.4.1 — 2025-11-27 — 🐛 Bug Fixes
|
|
85
|
+
- update build test to include postbuild (b1e2f48)
|
|
86
|
+
- add custom server.js for Plesk (b3912cd)
|
|
87
|
+
- migrate dashboard to Next.js with TypeScript and Tailwind CSS (bce1fec)
|
|
88
|
+
- fix package.json scripts (fb25e98)
|
|
89
|
+
- fix tsconfig and remove dist artifact (282759f)
|
|
90
|
+
|
|
91
|
+
## 1.4.0 — 2025-11-26
|
|
92
|
+
- See CHANGELOG for details.
|
|
93
|
+
|
|
94
|
+
## 1.3.11 — 2025-11-23
|
|
95
|
+
- Re-applied Plesk security fix (moved static files to `web/public/`).
|
|
96
|
+
- Updated build configuration and server paths.
|
|
97
|
+
|
|
98
|
+
## 1.3.10 — 2025-11-23
|
|
99
|
+
- Fixed workflow state synchronization issue that caused forced releases.
|
|
100
|
+
- Added `docs/WORKFLOW-BEST-PRACTICES.md`.
|
|
101
|
+
|
|
102
|
+
## 1.3.9 — 2025-11-23
|
|
103
|
+
- Improved documentation modal layout and readability.
|
|
104
|
+
|
|
105
|
+
## 1.3.8 — 2025-11-23
|
|
106
|
+
- Fixed documentation loading in production by tracking `dist/docs` in git.
|
|
107
|
+
|
|
108
|
+
## 1.3.0 — 2025-11-22
|
|
109
|
+
- Added comprehensive Antigravity integration documentation and examples.
|
|
110
|
+
- Fixed Windows shell escaping for commit messages.
|
|
111
|
+
- Fixed release scripts to support ESM projects.
|
|
112
|
+
- Release guard now delegates to `@programinglive/commiter` and verifies the package is installed before running.
|
|
113
|
+
|
|
114
|
+
## 1.2.7 — 2025-11-13
|
|
115
|
+
- Delegated release process to `@programinglive/commiter`.
|
|
116
|
+
|
|
117
|
+
## 1.2.6 — 2025-11-11
|
|
118
|
+
- Exposed primary branch helper in CLI.
|
|
119
|
+
- Updated documentation regarding commiter delegation.
|
|
120
|
+
|
|
121
|
+
> **Notice:** Versions 1.2.2 through 1.2.5 were published briefly for packaging experiments and have been withdrawn.
|
|
122
|
+
|
|
123
|
+
## 1.2.1 — 2025-11-03
|
|
124
|
+
- Packaging touch-up; functionality remains identical to 1.2.0.
|
|
125
|
+
|
|
126
|
+
## 1.2.0 — 2025-11-03
|
|
127
|
+
- Reload the workflow state from disk for every tool call, preventing stale data when multiple clients manipulate the same project.
|
|
128
|
+
|
|
129
|
+
## 1.1.18 — 2025-11-03
|
|
130
|
+
- `commit_and_push` now auto-detects the primary branch (preferring `main`, then `master`) when none is supplied.
|
|
131
|
+
|
|
132
|
+
## 1.1.17 — 2025-10-31
|
|
133
|
+
- Release bookkeeping only; no user-facing changes.
|
|
134
|
+
|
|
135
|
+
## 1.1.16 — 2025-10-31
|
|
136
|
+
- Added npm provenance metadata so published packages include supply-chain attestations.
|
|
137
|
+
|
|
138
|
+
## 1.1.15 — 2025-10-31
|
|
139
|
+
- Documented the automated npm publish workflow and ensured CI builds include provenance before publishing.
|
|
140
|
+
|
|
141
|
+
## 1.1.14 — 2025-10-31
|
|
142
|
+
- Improved project-root detection for workflow state, fixing issues when the server runs from nested directories.
|
|
143
|
+
|
|
144
|
+
## 1.1.13 — 2025-10-30
|
|
145
|
+
- Version bump to distribute refreshed dashboard assets; no new functionality beyond 1.1.12.
|
|
146
|
+
|
|
147
|
+
## 1.1.12 — 2025-10-30
|
|
148
|
+
- Added a `node index.js call <tool>` CLI helper to invoke MCP tools without a client integration.
|
|
149
|
+
- Refreshed the web dashboard with a docs modal, dedicated docs API endpoints, and streamlined navigation.
|
|
150
|
+
|
|
151
|
+
## 1.1.11 — 2025-10-30
|
|
152
|
+
- Introduced per-user workflow state stored under `.state/users/<id>/` to avoid collisions on shared repos.
|
|
153
|
+
- Added a SQLite-backed project knowledge summary and the dashboard that visualizes history and trends.
|
|
154
|
+
- Hardened resumable workflows by re-checking persisted summaries between steps.
|
|
155
|
+
|
|
156
|
+
## 1.1.10 — 2025-10-29
|
|
157
|
+
- Shipped the initial project knowledge library with a persisted JSON summary for future database integrations.
|
|
158
|
+
|
|
159
|
+
## 1.1.9 — 2025-10-29
|
|
160
|
+
- Made `run_full_workflow` resume intelligently from the current phase.
|
|
161
|
+
- Expanded automated tests around README/exec updates and other workflow paths.
|
|
162
|
+
|
|
163
|
+
## 1.1.8 — 2025-10-27
|
|
164
|
+
- Documented the `DEV_WORKFLOW_STATE_FILE` override for relocating workflow state outside the repository.
|
|
165
|
+
|
|
166
|
+
## 1.1.7 — 2025-10-26
|
|
167
|
+
- Added prompts guiding developers to document changes immediately after tests pass.
|
|
168
|
+
|
|
169
|
+
## 1.1.6 — 2025-10-26
|
|
170
|
+
- Prevented `.state` from being created at filesystem roots.
|
|
171
|
+
- Enforced that commits must land before any release action can run.
|
|
172
|
+
|
|
173
|
+
## 1.1.5 — 2025-10-25
|
|
174
|
+
- Introduced the release guard, blocking `npm run release:*` until every prerequisite tool has run.
|
|
175
|
+
- Standardized per-project workflow state creation during installs.
|
|
176
|
+
|
|
177
|
+
## 1.1.4 — 2025-10-25
|
|
178
|
+
- Ensured the install script always targets the project root when initializing `.state`.
|
|
179
|
+
|
|
180
|
+
## 1.1.3 — 2025-10-25
|
|
181
|
+
- Packaged the MCP server for project-level installs with per-project workflow state isolation.
|
|
182
|
+
|
|
183
|
+
## 1.1.2 — 2025-10-25
|
|
184
|
+
- Version alignment release with no additional changes versus 1.1.1.
|
|
185
|
+
|
|
186
|
+
## 1.1.1 — 2025-10-25
|
|
187
|
+
- Added `force_complete_task`, letting teams close tasks early with an audit trail.
|
|
188
|
+
|
|
189
|
+
## 1.1.0 — 2025-10-25
|
|
190
|
+
- Added smart staging checks before commit, and made `continue_workflow` auto-run the next action in the commit phase.
|
|
191
|
+
- Enabled clean-tree commits to utilize `commit_and_push` and `perform_release` without manual staging.
|
|
192
|
+
- Clarified documentation for the commit/push step.
|
|
193
|
+
|
|
194
|
+
## 1.0.11 — 2025-10-25
|
|
195
|
+
- Added contextual "continue workflow" guidance describing the next recommended tool.
|
|
196
|
+
- Blocked releases until commits are safely pushed.
|
|
197
|
+
|
|
198
|
+
## 1.0.10 — 2025-10-24
|
|
199
|
+
- Modularized the workflow server internals for maintainability.
|
|
200
|
+
- Expanded automated tests around the release push flow.
|
|
201
|
+
|
|
202
|
+
## 1.0.9 — 2025-10-23
|
|
203
|
+
- Documented how local workflow state is managed across projects.
|
|
204
|
+
|
|
205
|
+
## 1.0.8 — 2025-10-21
|
|
206
|
+
- Added explicit workflows for skipping tests with justification and dropping tasks mid-flight.
|
|
207
|
+
|
|
208
|
+
## 1.0.7 — 2025-10-20
|
|
209
|
+
- Version alignment update; no new functionality recorded.
|
|
210
|
+
|
|
211
|
+
## 1.0.6 — 2025-10-20
|
|
212
|
+
- Strengthened release tests to ensure prerequisites are met before tagging.
|
|
213
|
+
|
|
214
|
+
## 1.0.5 — 2025-10-20
|
|
215
|
+
- Updated tests around `workflowState` persistence and validation.
|
|
216
|
+
|
|
217
|
+
## 1.0.4 — 2025-10-20
|
|
218
|
+
- Added an enforced release step after the ready check to ensure workflow order.
|
|
219
|
+
- Improved Windows compatibility by quoting commit messages safely.
|
|
220
|
+
|
|
221
|
+
## 1.0.3 — 2025-10-20
|
|
222
|
+
- Added a project `.gitignore` and clarified cross-platform installation steps.
|
|
223
|
+
|
|
224
|
+
## 1.0.2 — 2025-10-19
|
|
225
|
+
- Hardened `run_tests` argument validation and normalized tool call arguments.
|
|
226
|
+
- Expanded documentation around tool payload requirements.
|
|
227
|
+
|
|
228
|
+
## 1.0.1 — 2025-10-18
|
|
229
|
+
- Configured release tooling to support semantic version tagging moving forward.
|
|
230
|
+
|
|
231
|
+
## 1.0.0 — 2025-10-18
|
|
232
|
+
- Initial public release with the full MCP workflow (start → fix → tests → docs → commit → release → complete).
|
|
233
|
+
- Launched project governance, contribution guidelines, and tooling scaffolding.
|