@sabaiway/agent-workflow-kit 1.37.0 → 1.37.1

package/CHANGELOG.md

@@ -4,6 +4,22 @@ Semantically versioned ([semver](https://semver.org)), newest first. The `versio
 is the current release. `upgrade` mode reads a project's `docs/ai/.workflow-version` and applies
 every `migrations/<version>-<slug>.md` newer than it, in semver order.
 
+## 1.37.1 — Fix: the fold-completeness probe on Node 18/20 counted pattern-filtered SKIP lines as executed tests
+
+A **patch** release (one product fix + its pinned fixtures; no other change). On Node 18/20 —
+versions the kit supports — `node --test --test-name-pattern` EMITS every non-matching test as
+`ok N - <name> # SKIP test name does not match pattern` (newer Node omits them), so the 1.37.0
+probe parser counted those lines as real matches: a `testId` whose pattern matches NOTHING was
+reported **resolvable with a green baseline**, and the fold-completeness gate green-vouched a test
+that never ran — defeating the gate's purpose on exactly those Node versions. Caught by the CI
+matrix (node 18 + 20) on the 1.37.0 release commit; invisible on newer local Node.
+
+- `parseProbeOutput` now ignores any TAP result line carrying a **SKIP/TODO directive** — a skipped
+  test was not executed, on any Node version; a real test name containing a literal `# skip` would
+  only fail CLOSED (unresolvable), never open.
+- New pinned fixtures: the node-18/20 pattern-filter TAP shape (nomatch → unresolvable; a matched
+  test among skipped ones still resolves), a lowercase `# skip`, and a `# TODO` directive.
+
 ## 1.37.0 — Fold-safety completion: a fixable-bug requires its test, and a coverage gate attests the fold against the changed code (AD-046)
 
 A **feature** release (deployment-lineage head stays `1.3.0` — no migration). AD-045's ledger computed

package/SKILL.md

@@ -3,7 +3,7 @@ name: agent-workflow-kit
 description: Deploy or upgrade a portable AI-agent memory-and-workflow system in any project. Use when the user wants to bootstrap `docs/ai/` + an entry-point `AGENTS.md` (+ `CLAUDE.md` alias) + cap/archive/index enforcement in a new or existing repo, set up the Memory Map and session protocols, install the docs-rotation pre-commit hook, or run `/agent-workflow-kit` / `/agent-workflow-kit upgrade`. Triggers on phrases like "set up the memory system", "deploy the AI workflow here", "bootstrap docs/ai", "upgrade the workflow".
 disable-model-invocation: true
 metadata:
-  version: '1.37.0'
+  version: '1.37.1'
 ---
 
 # agent-workflow-kit

package/capability.json

@@ -3,7 +3,7 @@
   "schema": 1,
   "name": "agent-workflow-kit",
   "kind": "composition-root",
-  "version": "1.37.0",
+  "version": "1.37.1",
   "provides": [],
   "roles": {},
   "detect": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sabaiway/agent-workflow-kit",
-  "version": "1.37.0",
+  "version": "1.37.1",
   "description": "Portable, cross-agent memory & workflow for AI coding agents — Claude Code, Codex, Cursor, Devin Desktop. One command deploys an AGENTS.md entry point + docs/ai context with cap/archive/index enforcement into any repo.",
   "keywords": [
     "ai-agents",

package/tools/fold-completeness-run.mjs

@@ -180,15 +180,20 @@ export const computeUncoveredLines = ({ perProcessRanges, sourceText, changedLin
 
 const PROBE_RESULT_RE = /^(?:ok|not ok) \d+ - (.*)$/; // a column-0 TAP result line
 const PROBE_FAIL_RE = /^# fail (\d+)$/;
+const PROBE_DIRECTIVE_RE = /#\s*(?:skip|todo)\b/i; // a TAP SKIP/TODO directive — the test did NOT run
 
 // parseProbeOutput({ stdout, code, fileArg }) → { resolvable, executed, baselineGreen }. A node:test
 // run with a pattern that matches NOTHING emits only a file-wrapper result whose description is the
-// file path itself (`ok N - <file>`); a real match emits the test NAME. So `resolvable` = at least one
-// column-0 result whose description is not the file we passed; `baselineGreen` = resolvable AND the run
-// was green (exit 0 and `# fail 0`). The wrapper is matched by BASENAME, not literally: node normalizes
-// the echoed path ('./x' → 'x', or an absolute path), so a literal desc===fileArg compare would count
-// the wrapper as a real match and falsely report resolvable/green (codex R1). A basename compare is
-// invariant to ./ / abs / rel; a real test name colliding with the file's basename is absurd and would
+// file path itself (`ok N - <file>`) on newer node — but node 18/20 ALSO emit every pattern-FILTERED
+// test as `ok N - <name> # SKIP test name does not match pattern`, so a result line carrying a TAP
+// SKIP/TODO directive must never count: the test was not executed, and counting it green-vouches a
+// nonexistent testId on exactly the node versions the kit supports (caught by CI's 18/20 matrix).
+// So `resolvable` = at least one column-0, directive-free result whose description is not the file we
+// passed; `baselineGreen` = resolvable AND the run was green (exit 0 and `# fail 0`). The wrapper is
+// matched by BASENAME, not literally: node normalizes the echoed path ('./x' → 'x', or an absolute
+// path), so a literal desc===fileArg compare would count the wrapper as a real match and falsely
+// report resolvable/green (codex R1). A basename compare is invariant to ./ / abs / rel; a real test
+// name colliding with the file's basename — or containing a literal "# skip" — is absurd and would
 // only fail CLOSED (mark unresolvable), never open.
 export const parseProbeOutput = ({ stdout, code, fileArg }) => {
   let matched = 0;
@@ -196,7 +201,7 @@ export const parseProbeOutput = ({ stdout, code, fileArg }) => {
   const wanted = basename(String(fileArg).trim());
   for (const line of String(stdout).split('\n')) {
     const m = PROBE_RESULT_RE.exec(line);
-    if (m && basename(m[1].trim()) !== wanted) matched += 1;
+    if (m && !PROBE_DIRECTIVE_RE.test(m[1]) && basename(m[1].trim()) !== wanted) matched += 1;
     const f = PROBE_FAIL_RE.exec(line.trim());
     if (f) failCount = Number(f[1]);
   }