qatools-cli 1.2.38 → 1.2.39

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.
Files changed (2) hide show
  1. package/mcp-core.js +1 -1
  2. package/package.json +1 -1
package/mcp-core.js CHANGED
@@ -96,7 +96,7 @@ Steps, in order:
96
96
  2. Build one approved wish: list_requirements status approved; take the first that a wish links to (its requirementKey) and that is not started. Then:
97
97
  - update_requirement status in_progress, assignedTo "me"; comment in the wish that you have started.
98
98
  - git switch -c loop/<requirement key> from the main branch (git pull first). Implement it the way the repo already works (read CLAUDE.md and the code around it). Add or extend automated tests for its acceptance criteria.
99
- - Run the repo's tests and build. If they fail and you cannot fix it: commit the work in progress on the branch, push the branch, set the requirement back to approved, and comment in the wish what stops you, in plain words. Stop.
99
+ - Run the repo's tests and build in a mode that ends by itself (no watch mode: e.g. --watch=false, CI=true; tests in a subfolder with npm test --prefix <folder>). If they fail and you cannot fix it: commit the work in progress on the branch, push the branch, set the requirement back to approved, and comment in the wish what stops you, in plain words. Stop.
100
100
  - When everything passes: commit (the message names the requirement key), push the branch, open a pull request if gh is available.
101
101
  - Test environment: get_app_context. If its environments list one named test (or Test, staging), deploy the branch there with the repo's own documented test deploy, and check that the change works there. If there is none, do NOT deploy.
102
102
  - update_requirement status implemented with evidence: the test output (numbers), the branch and commit, and the test address if deployed.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "qatools-cli",
3
- "version": "1.2.38",
3
+ "version": "1.2.39",
4
4
  "description": "CLI for QA Tools — requirements, epics, sprints, sessions, App Context sync, project agenda. The companion to qa-tools.com.",
5
5
  "scripts": {
6
6
  "release": "npm version patch --no-git-tag-version && npm publish",