@curdx/flow 7.1.21 → 7.1.22
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/CHANGELOG.md +18 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,24 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to `@curdx/flow` are documented here. Format follows [Keep a Changelog](https://keepachangelog.com/) and the project follows [Semantic Versioning](https://semver.org/).
|
|
4
4
|
|
|
5
|
+
## 7.1.22 — 2026-05-11
|
|
6
|
+
|
|
7
|
+
### Added
|
|
8
|
+
|
|
9
|
+
- **Browser verification policy for full-stack delivery.** Added a plugin reference that standardizes Playwright CLI as the default repeatable E2E path and Chrome DevTools MCP as the high-fidelity path for GIS, WebGL, canvas, map, GPU, console, network, performance, and flaky Playwright cases.
|
|
10
|
+
- **Browser readiness in `curdx-flow doctor`.** Doctor output now reports detected dev-server scripts, E2E scripts, browser automation dependencies, Playwright config files, chrome-devtools-mcp dependency declaration, and local Chrome availability.
|
|
11
|
+
|
|
12
|
+
### Changed
|
|
13
|
+
|
|
14
|
+
- **Task planning now requires an explicit Browser Verify decision.** `task-planner`, `/curdx-flow:tasks`, VE references, and task templates now require `playwright`, `chrome-devtools-mcp`, `none`, or `blocked` before implementation tasks.
|
|
15
|
+
- **Executor and QA prompts enforce browser evidence.** `spec-executor`, `qa-engineer`, and `verification-before-completion` now reject browser-facing completion claims without fresh Playwright or Chrome DevTools MCP evidence, and explicitly avoid `/ultrareview` as a verification path.
|
|
16
|
+
- **Research output feeds browser verification.** `research-analyst` now records Browser Verify strategy alongside dev server, E2E config, browser dependency, port, and health endpoint discovery.
|
|
17
|
+
|
|
18
|
+
### Tests
|
|
19
|
+
|
|
20
|
+
- Added runtime CLI coverage for browser readiness in `doctor` output and manifest-integrity coverage that keeps the browser verification policy linked into planning, execution, QA, and skill surfaces.
|
|
21
|
+
- Verified with `npm run verify`.
|
|
22
|
+
|
|
5
23
|
## 7.1.21 — 2026-05-11
|
|
6
24
|
|
|
7
25
|
### Added
|