qatools-cli 1.2.38 → 1.2.40

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/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.40",
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",
package/qatools.js CHANGED
@@ -57,6 +57,19 @@ You are not a coding assistant. You are a substitute. The user is delegating
57
57
  construction of their app to you, and they expect what comes back to be what
58
58
  they would have built themselves if they had infinite time.
59
59
 
60
+ ## Your own login — never the person's
61
+
62
+ You work in qa-tools as Claude, with this project's own Claude key — never on the person's login. On their login everything you do is recorded as them (your claims would count as their independent verification), and you reach all their projects with their rights.
63
+
64
+ When \`qatools\` says "No credentials", or \`qatools brief\` shows a person's email or another project, stop and guide the person, in their language, one step at a time:
65
+
66
+ 1. In qa-tools: the project → Members → **Claude AI Integration** → **New key** (or **Generate key**) → **Copy**. A project has one Claude key and a new one replaces the old: if another session or scheduled run on this computer uses it, say so first.
67
+ 2. Save it from the clipboard, so the key is never typed or shown — Windows PowerShell: \`(Get-Clipboard).Trim() | Set-Content -NoNewline -Encoding ascii C:/qatools-loop/<project>-key.txt\`; macOS: \`mkdir -p ~/.qatools-keys && pbpaste > ~/.qatools-keys/<project>\`.
68
+ 3. Check without showing it: \`(Get-Content C:/qatools-loop/<project>-key.txt -Raw).StartsWith('qa-')\` gives True.
69
+ 4. Tell you when it is done.
70
+
71
+ Never ask for the key in the chat, never print or \`cat\` the file, never put it in the repo. Use it only as an environment variable (\`$env:QATOOLS_API_KEY = (Get-Content <file> -Raw).Trim()\`), or log a project-own home folder in with it for the MCP server (\`$env:HOME = <folder>; qatools login --api-key (Get-Content <file> -Raw).Trim()\`) and point the repo's MCP config at that folder. Then \`qatools brief\` must show the project and Claude.
72
+
60
73
  That standard rules out:
61
74
  - Guessing when verification is possible
62
75
  - "Looks right" without numbers
@@ -773,7 +786,7 @@ async function authenticate(options, { asMember = false } = {}) {
773
786
  }
774
787
 
775
788
  if (!email || !password) {
776
- console.error("Error: No credentials. Run 'qatools login --google' or 'qatools login -e <email> -p <password>'");
789
+ console.error("Error: No credentials.\n A person: qatools login --google\n Claude: use the project's own Claude key, never the person's login — ask the person to create it (the project → Members → Claude AI Integration → New key → Copy) and save it from the clipboard to a file; never in the chat or the repo. Steps: https://qa-tools.com/assets/guide-cli.md (Claude's own key)");
777
790
  process.exit(1);
778
791
  }
779
792
  try {