yadflow 2.9.0 → 2.10.0

package/CHANGELOG.md

@@ -1,9 +1,9 @@
-# [2.9.0](https://github.com/abdelrahmannasr/yadflow/compare/v2.8.0...v2.9.0) (2026-06-15)
+# [2.10.0](https://github.com/abdelrahmannasr/yadflow/compare/v2.9.0...v2.10.0) (2026-06-15)
 
 
 ### Features
 
-* **docs:** enhance interactive docs — clearer diagram, brand icon, dimmed stubs ([#65](https://github.com/abdelrahmannasr/yadflow/issues/65)) ([969a20d](https://github.com/abdelrahmannasr/yadflow/commit/969a20dc1e9778e1ffd0962e557f3e2c28dfd6ef))
+* **checks:** cap jest/vitest test workers in connected-repo CI gates ([#66](https://github.com/abdelrahmannasr/yadflow/issues/66)) ([7a16d51](https://github.com/abdelrahmannasr/yadflow/commit/7a16d51eb135c3240d3e94012f844c8b74210bd9))
 
 # [2.2.0](https://github.com/abdelrahmannasr/yadflow/compare/v2.1.0...v2.2.0) (2026-06-14)
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "yadflow",
-  "version": "2.9.0",
+  "version": "2.10.0",
   "description": "Yadflow — the gated, team, multi-repo SDLC: author → review → build with a PR-driven review gate and a zero-dependency `yad` CLI (setup, gate, commit, open-pr, ship, repo). A BMAD module + 29 yad-* skills.",
   "type": "module",
   "author": "AbdelRahman Nasr",

package/skills/yad-checks/SKILL.md

@@ -16,6 +16,8 @@ in CI on every PR/MR and must pass before merge (build plan §C). Each is a smal
    contract upstream, it **FAILS and routes back to the architecture gate**. The shared surface is
    never widened from inside a code repo (Phase 2 contract representation: delimited block + SHA-256 lock).
 3. **build/test/lint** — standard quality stage; tests must actually exercise new behavior, not just pass.
+   The CI job sets `YAD_TEST_MAX_WORKERS` (default `2`); the gate caps jest/vitest test concurrency at
+   that and is a no-op for other runners (see `references/check-gates.md`).
 4. **verified-commits** — no unverified commits from unverified users: every commit in the range must
    carry a signature the platform marks **Verified** AND be authored by a known identity
    (`.sdlc/verified-authors`, generated from the hub roster's `email` fields). Enforced on the

package/skills/yad-checks/references/check-gates.md

@@ -46,6 +46,11 @@ repo uses. Each reads conventions established by earlier steps — it invents no
 - Runs `npm run lint`, `npm run build`, `npm test` in order; any non-zero exit fails the gate.
 - Tests must actually exercise behavior (build plan §C) — an empty or trivially-passing suite does not
   satisfy the gate's intent.
+- **Test worker cap.** When the CI job sets `YAD_TEST_MAX_WORKERS` (the templates default it to `2`)
+  and the repo's `test` script is jest/vitest, the gate forwards `--maxWorkers=<n>` to bound CI
+  concurrency. For any other runner (`node --test`, mocha, …) it is a no-op — the flag is never
+  passed, so the gate cannot break on an unknown option. Override it per repo via the
+  `YAD_TEST_MAX_WORKERS` CI variable, or unset it to remove the cap.
 
 ### Canonical `package.json` scripts (Node demo)
 

package/skills/yad-checks/templates/checks/build-test-lint.sh

@@ -8,7 +8,19 @@ echo "[build/test/lint] lint…"
 npm run --silent lint
 echo "[build/test/lint] build…"
 npm run --silent build
+
+# Worker cap: when YAD_TEST_MAX_WORKERS is set AND the repo's test script is jest/vitest (the
+# runners that accept --maxWorkers), forward it to bound CI test concurrency. For any other runner
+# (node --test, mocha, …) it is a deliberate no-op so the gate never breaks on an unknown flag.
+extra=""
+if [ -n "${YAD_TEST_MAX_WORKERS:-}" ]; then
+  case "$(npm pkg get scripts.test 2>/dev/null || true)" in
+    *jest*|*vitest*) extra="-- --maxWorkers=${YAD_TEST_MAX_WORKERS}" ;;
+  esac
+fi
 echo "[build/test/lint] test…"
-npm run --silent test
+# Intentional word-splitting: $extra is either empty or `-- --maxWorkers=N`.
+# shellcheck disable=SC2086
+npm run --silent test $extra
 
 echo "PASS [build/test/lint]: lint, build, and tests all green."

package/skills/yad-checks/templates/github/yad-checks.yml

@@ -25,6 +25,8 @@ jobs:
 
   build-test-lint:
     runs-on: ubuntu-latest
+    env:
+      YAD_TEST_MAX_WORKERS: "2" # cap jest/vitest test workers in CI; ignored by other runners
     steps:
       - uses: actions/checkout@v4
         with: { fetch-depth: 0 }

package/skills/yad-checks/templates/gitlab/yad-checks.gitlab-ci.yml

@@ -42,6 +42,8 @@ yad-contract-check:
 yad-build-test-lint:
   extends: .sdlc_mr_only
   needs: []
+  variables:
+    YAD_TEST_MAX_WORKERS: "2" # cap jest/vitest test workers in CI; ignored by other runners
   script:
     - bash checks/build-test-lint.sh