yadflow 4.0.0-next.4 → 4.0.1

package/bin/yad.mjs

@@ -948,7 +948,7 @@ main()
   })
   .catch(async (err) => {
     // Under --json every failure is still one object on stdout (E1) — a refusal from the parser, a
-    // thrown YadError, a bug. The `code` is the `YAD-` code README "Troubleshooting" is keyed on.
+    // thrown YadError, a bug. The `code` is the `YAD-` code the docs/CLI.md "Error codes" table is keyed on.
     // If the command had already answered, stdout holds its object, and the failure goes to stderr.
     if (inJSON() && !jsonEmitted()) {
       if (err?.parsedCmd !== undefined && runningCmd === null) beginJSON(commandName(err.parsedWords ?? []));
@@ -959,7 +959,7 @@ main()
     const code = err?.code && /^YAD-/.test(err.code) ? ` [${err.code}]` : '';
     log(c.red(`\nyad failed${code}: ${err?.message || err}`));
     if (err?.hint) log(c.yellow(`  → ${err.hint}`));
-    if (code) log(c.dim('  (see README "Troubleshooting" for this code, or run `yad doctor`)'));
+    if (code) log(c.dim('  (see the error codes in https://github.com/abdelrahmannasr/yadflow/blob/main/docs/CLI.md#error-codes, or run `yad doctor`)'));
     process.exitCode = 1;
     // Offer to report the failure — but only interactively (never in CI), and opt-out via
     // YAD_NO_REPORT. `report` failing on its own would land here, so never re-offer for it.

package/cli/capture.mjs

@@ -319,7 +319,7 @@ export async function runCapture(root, { hook = false, noPush = false, now = Dat
     // secret captured by mistake, say) is not continued from a stale copy (E43 review 3). This prune clears
     // every stale copy on the hand path; a LOCAL branch is still pushed back, and the hook, which never
     // fetches, still reads a copy another fetch left. Removing one for good means `git branch -D` and
-    // `git branch -dr origin/…` on every machine too (README). The same
+    // `git branch -dr origin/…` on every machine too (docs/CLI.md, Background capture). The same
     // low-speed limit as the push, so a stalled HTTPS connection gives up instead of holding the capture.
     spawnSync('git', ['-c', 'http.lowSpeedLimit=1000', '-c', 'http.lowSpeedTime=20', 'fetch', '--quiet', '--prune', '--no-tags', 'origin', `+refs/heads/${WIP_PREFIX}/${name}/*:refs/remotes/origin/${WIP_PREFIX}/${name}/*`],
       { cwd: root, stdio: 'ignore', timeout: 30_000, env: { ...env, ...pushEnv(env) } });

package/cli/claims.mjs

@@ -22,7 +22,7 @@
 // may lose the race in silence. Nothing reads those copies while the local branch exists, and a capture by
 // hand fetches (with prune) before it relies on them.
 //
-// LIMITS, said in the README: capture off, or offline, is invisible; the push runs at most every 5 minutes;
+// LIMITS, said in docs/CLI.md (claims): capture off, or offline, is invisible; the push runs at most every 5 minutes;
 // two people with one git name share branches, so they never see each other; clocks are the committer's.
 import { spawnSync } from 'node:child_process';
 import fs from 'node:fs';

package/cli/errors.mjs

@@ -1,5 +1,5 @@
 // Structured error codes for the `yad` CLI. A YadError carries a stable code (greppable,
-// documented in README "Troubleshooting") and a one-line recovery hint that the top-level
+// documented in docs/CLI.md "Error codes") and a one-line recovery hint that the top-level
 // catch in bin/yad.mjs prints after the message. Plain Errors still work everywhere; codes
 // are reserved for the failures users actually hit and need to act on.
 export class YadError extends Error {
@@ -11,7 +11,7 @@ export class YadError extends Error {
   }
 }
 
-// The catalog — single source for doctor, the top-level catch, and the README table.
+// The catalog — single source for doctor, the top-level catch, and the docs/CLI.md table.
 export const CODES = {
   'YAD-ENV-001': 'git is not installed or not on PATH',
   'YAD-ENV-002': 'the platform CLI (gh/glab) is missing or not authenticated',

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "yadflow",
-  "version": "4.0.0-next.4",
-  "description": "Yadflow — the gated, team, multi-repo SDLC: author → review → build with a PR-driven review gate and a zero-dependency `yad` CLI (new/init/join, next, gate, capture/fold, commit/ship, repo, thread, history, doctor/migrate/update). Plus 38 yad-* skills.",
+  "version": "4.0.1",
+  "description": "Shared project memory and workflows for teams building with AI: a versioned record of plans, decisions, contracts and reviews across repos, human-approved review gates, and a zero-dependency `yad` CLI plus 38 skills for your AI assistant.",
   "type": "module",
   "author": "AbdelRahman Nasr",
   "license": "MIT",
@@ -46,7 +46,7 @@
     "test:e2e": "bash test/e2e/run.sh",
     "release-check": "bash scripts/release-check.sh",
     "coverage": "node --test --experimental-test-coverage --test-coverage-exclude='cli/test*.mjs' --test-coverage-exclude='cli/test*.js' --test-coverage-lines=70 --test-coverage-branches=70 cli/test.mjs cli/test-checks.mjs cli/test-threads.mjs cli/test-golden.mjs cli/test-migrate.mjs cli/test-hooks.mjs cli/test-fuzz.js",
-    "diagrams": "npx -y @mermaid-js/mermaid-cli -i docs/diagrams/sdlc-overview.mmd -o docs/diagrams/sdlc-overview.svg -b transparent && npx -y @mermaid-js/mermaid-cli -i docs/diagrams/review-loop.mmd -o docs/diagrams/review-loop.svg -b transparent",
+    "diagrams": "npx -y @mermaid-js/mermaid-cli@11.15.0 -i docs/diagrams/sdlc-overview.mmd -o docs/diagrams/sdlc-overview.svg -b transparent && npx -y @mermaid-js/mermaid-cli@11.15.0 -i docs/diagrams/review-loop.mmd -o docs/diagrams/review-loop.svg -b transparent && npx -y @mermaid-js/mermaid-cli@11.15.0 -i docs/diagrams/work-and-memory.mmd -o docs/diagrams/work-and-memory.svg -b transparent && npx -y @mermaid-js/mermaid-cli@11.15.0 -i docs/diagrams/feature-evolution.mmd -o docs/diagrams/feature-evolution.svg -b transparent",
     "prepublishOnly": "npm test"
   },
   "keywords": [