@dzhechkov/keysarium 1.5.40 → 1.5.41

package/.dz-manifest.json

@@ -5,7 +5,7 @@
     "files": [
       {
         "path": "README.md",
-        "sha256": "676f962e26cf674631c11f1593d533fa1e9c4cdee7e1d7786f7727fc1412366a"
+        "sha256": "55a9e601a7028333e77dd2ee0f8eec201f053cd970deb8f58ecfa7cf06987cf4"
       },
       {
         "path": "README.ru.md",
@@ -17,7 +17,7 @@
       },
       {
         "path": "package.json",
-        "sha256": "7b17d0b5b5a60c3ee74d7d93358040a1353c828a962df2530ba74dc982309089"
+        "sha256": "9371c3fe3922382a7871224941fb0bae838dfcbeb750bd55a662e4c27a1e1af7"
       },
       {
         "path": "src/cli.js",
@@ -381,7 +381,7 @@
       },
       {
         "path": "templates/.claude/skills/feature-adr/modules/06-implementation-plan.md",
-        "sha256": "3903e2694ad47782914b35869bbf19c5f0803b6dafdcfb629df343a5ff00d1b9"
+        "sha256": "b3efdfa1d44f4c51ff46551b5827066955c1f0bfee212d371ac1e2fb1c99980f"
       },
       {
         "path": "templates/.claude/skills/feature-adr/modules/07-code.md",
@@ -481,7 +481,7 @@
       },
       {
         "path": "templates/.claude/skills/feature-adr/scripts/check-plan-completeness.mjs",
-        "sha256": "5cef77e68c58f163be64516013fb90866ef7201e415dc8888cc21a0f4d92b7d8"
+        "sha256": "eddf116620050e80b88497ace026fb8e0a12986f94f216181480c7daa0e08be4"
       },
       {
         "path": "templates/.claude/skills/frontend-design/LICENSE.txt",
@@ -985,5 +985,5 @@
       }
     ]
   },
-  "signature": "HqvQFasiKkM8l4ksIkFcAGUHMtxvogzo9q7bO3Km4i2EQPoxwyWo6Z85GftW6HRLA+L75kTNPWpMU5avuxmJBA=="
+  "signature": "AXc5drN9RLQVp4PK9QbjYylVG4nQruSrJQZV4KPQ2JY3/Xif4oZzOxlUOQ1JA5+HRppGUvGnnMtTN8c35rDkDw=="
 }

package/README.md

@@ -419,6 +419,12 @@ deliberately excluded — "skeleton first" is nonsense there.
 
 ## Status
 
+`1.5.41` — refreshes the bundled `feature-adr` gate script with the C6 amendment-integrity fix (each
+amendment scoped to its own block; closes a false refusal on markers below the old three-line window
+AND a false pass where a testless amendment borrowed its neighbour's marker). No keysarium behaviour
+changes. See `@dzhechkov/skills-feature-adr@1.5.3`.
+
+
 `1.5.38` — a fix to the bundled `feature-adr` gate script in `templates/`, no pipeline change.
 
 The bundled K2 plan-completeness gate now tells an **ABSENT** `00_complexity_assessment.md` from a
@@ -427,5 +433,5 @@ carrying no acid table is an honest SKIP. Both used to report as a clean skip, s
 silently switched itself off whenever Step 0 wrote nothing — MEASURED 2026-08-21, 66 of 199 features
 carried that file and the last four in a row did not.
 
-`1.5.40` — the bundled `feature-adr` Step-8 module now describes the amendment gate as the command
+`1.5.41` — the bundled `feature-adr` Step-8 module now describes the amendment gate as the command
 `dz amendment-check` instead of a judgement the reviewer is asked to make. Text only; no pipeline change.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dzhechkov/keysarium",
-  "version": "1.5.40",
+  "version": "1.5.41",
   "description": "AI Case Research Toolkit for Claude Code — full 7-phase pipeline with feature-adr, dream cycles, background workers, multi-platform support, reward learning, and Cloud.ru AI Factory mapping (--ai-factory flag)",
   "main": "src/cli.js",
   "bin": {

package/sbom.json

@@ -15,7 +15,7 @@
       "hashes": [
         {
           "alg": "SHA-256",
-          "content": "676f962e26cf674631c11f1593d533fa1e9c4cdee7e1d7786f7727fc1412366a"
+          "content": "55a9e601a7028333e77dd2ee0f8eec201f053cd970deb8f58ecfa7cf06987cf4"
         }
       ]
     },
@@ -45,7 +45,7 @@
       "hashes": [
         {
           "alg": "SHA-256",
-          "content": "7b17d0b5b5a60c3ee74d7d93358040a1353c828a962df2530ba74dc982309089"
+          "content": "9371c3fe3922382a7871224941fb0bae838dfcbeb750bd55a662e4c27a1e1af7"
         }
       ]
     },
@@ -955,7 +955,7 @@
       "hashes": [
         {
           "alg": "SHA-256",
-          "content": "3903e2694ad47782914b35869bbf19c5f0803b6dafdcfb629df343a5ff00d1b9"
+          "content": "b3efdfa1d44f4c51ff46551b5827066955c1f0bfee212d371ac1e2fb1c99980f"
         }
       ]
     },
@@ -1205,7 +1205,7 @@
       "hashes": [
         {
           "alg": "SHA-256",
-          "content": "5cef77e68c58f163be64516013fb90866ef7201e415dc8888cc21a0f4d92b7d8"
+          "content": "eddf116620050e80b88497ace026fb8e0a12986f94f216181480c7daa0e08be4"
         }
       ]
     },

package/templates/.claude/skills/feature-adr/modules/06-implementation-plan.md

@@ -185,6 +185,11 @@ Create `features/<slug>/06_implementation_plan.md` with:
 - `## Amendments` — every correction folded into this plan (a Step-3.5 CONDITIONAL condition, a
   challenge-panel confirmed finding, a user checkpoint steer) as a fixed-shape row:
   `AM-N (source): <change>. Confirmation: <property> → test `test_name` (fails if reverted).`
+  The row is MACHINE-READ by the K2 C6 gate: the `→ test \`name\`` marker (or `superseded by AM-N`)
+  must sit inside that amendment's OWN block — anywhere between its `AM-N` line and the line where
+  the NEXT `AM-N` begins. Multi-line amendments are fine; what is NOT fine is putting a marker after
+  the following amendment has already started, because it then belongs to that one. A bare range
+  like `AM-1..AM-4` never opens a row.
   A safeguard amendment's named test must prove it TRIGGERS on a real input, not merely that its code
   path exists. Step 8 verifies every named test exists and is non-vacuous (`dz discrimination-check`).
 

package/templates/.claude/skills/feature-adr/scripts/check-plan-completeness.mjs

@@ -327,13 +327,36 @@ else for (const t of acidTokens) if (!new RegExp(`\\b${t.replace(/[.*+?^${}()|[\
     }
   }
   if (sectionStart >= 0) {
-    for (const lnRaw of amSection.split('\n')) {
-      const ln = lnRaw.trim();
-      const am = /^(?:[-*|]\s*)?\*{0,2}(AM-(?:CP-)?\d+)\*{0,2}\b/.exec(ln);
-      if (!am) continue;
-      const hasTest = /\u2192\s*test\b|->\s*test\b/.test(ln) || /\u2192\s*test\b|->\s*test\b/.test(amSection.slice(amSection.indexOf(lnRaw)).split('\n').slice(0, 3).join('\n'));
-      const superseded = /superseded by AM-(?:CP-)?\d+/i.test(ln);
-      if (!hasTest && !superseded) failures.push(`C6: ${am[1]} carries neither \`\u2192 test <name>\` nor \`superseded by AM-N\` — an amendment without a confirmation is a wish, and a retracted one must say its successor`);
+    // Each amendment's confirmation is looked for in ITS OWN BLOCK: from its definition line to the
+    // line where the NEXT amendment begins. Three defects die with the old three-line window
+    // (MEASURED 2026-08-25 against the 142-plan corpus — 292 C6 failures before, 33 after, and ZERO
+    // rows newly caught that pass today):
+    //   • FALSE REFUSAL — a marker on the `Confirmation:` line 4+ lines down was invisible, so plans
+    //     that DID name their test were rejected (7 per run, twice in one day, on a user's machine).
+    //   • FALSE PASS — the window is three LINES, not one amendment, so `- AM-1 testless` followed by
+    //     `- AM-2 … -> test x` PASSED: AM-1 borrowed its neighbour's marker. That is the safety half,
+    //     and it is why the boundary is the next DEFINITION rather than a blank line — a blank line
+    //     does not separate adjacent bullet rows.
+    //   • A substring seek (`amSection.indexOf(lnRaw)`) let a duplicated line read someone else's
+    //     window. Indices remove that hazard for free.
+    // The boundary is not invented: parseAmendments() in harness-core/src/amendment-trace.ts has used
+    // the same next-definition bound all along, so this also ends a divergence between two checkers.
+    const secLines = amSection.split('\n');
+    // The bullet stays OPTIONAL: requiring it drops 104 of the corpus's 347 real AM rows out of the
+    // check entirely (MEASURED). The `(?!\s*\.)` guard is what refuses a wrapped `AM-1..AM-4;`
+    // range preamble, which used to open a phantom amendment and double-count AM-1 — it costs 0 rows.
+    const DEF = /^(?:[-*|]\s*)?\*{0,2}(AM-(?:CP-)?\d+)\*{0,2}\b(?!\s*\.)/;
+    // `tests?` — the two-id form `-> tests \`a\` and \`b\`` is corpus-canonical and is what
+    // amendment-trace.ts parses; matching only the singular turned two currently-green rows red.
+    const MARK = /\u2192\s*tests?\b|->\s*tests?\b/;
+    const defs = [];
+    secLines.forEach((l, i) => { const m = DEF.exec(l.trim()); if (m) defs.push({ i, id: m[1] }); });
+    for (let k = 0; k < defs.length; k++) {
+      const to = k + 1 < defs.length ? defs[k + 1].i : secLines.length;
+      const block = secLines.slice(defs[k].i, to).join('\n');
+      const hasTest = MARK.test(block);
+      const superseded = /superseded by AM-(?:CP-)?\d+/i.test(block);
+      if (!hasTest && !superseded) failures.push(`C6: ${defs[k].id} carries neither \`\u2192 test <name>\` nor \`superseded by AM-N\` — an amendment without a confirmation is a wish, and a retracted one must say its successor`);
     }
   }
 }