@dzhechkov/skills-feature-adr 1.5.7 → 1.5.10

package/.dz-manifest.json

@@ -13,7 +13,7 @@
       },
       {
         "path": "README.md",
-        "sha256": "4ab808507be5c64cfa7b74ef3c186145d0654cd9c2fad86229685edaac6edb10"
+        "sha256": "b1dbcb7b1f0f3d95bdda9f9568f65e1f78b306b2cb64e42979b1981aeadc6047"
       },
       {
         "path": "bin/cli.js",
@@ -25,7 +25,7 @@
       },
       {
         "path": "package.json",
-        "sha256": "1efad8edf817286284ef35578e3b5046205350603b7e9cb9b979993a69f85c8a"
+        "sha256": "e376fe73743953ad7f0b7525e22f815ea949450fe7ea784f89d1e61bcc62ce6f"
       },
       {
         "path": "src/cli.js",
@@ -249,7 +249,7 @@
       },
       {
         "path": "templates/.claude/skills/feature-adr/scripts/check-plan-completeness.mjs",
-        "sha256": "630eb9047258ad0333082f407cd34522e4c278650f22ef6dba1ef897ec5cce71"
+        "sha256": "cd2d4e05d1b61be5485c9836abdebdb00b5f4085a14f3c71126cc45d4e08fe3b"
       },
       {
         "path": "templates/.claude/skills/frontend-design/LICENSE.txt",
@@ -313,7 +313,7 @@
       },
       {
         "path": "templates/.claude/workflows/feature-adr.js",
-        "sha256": "f5454faf9cca12a3cbef5444a3fe586823bfe2a164ab391c9589ed206a0b9b9f"
+        "sha256": "ef6a119466e504307116b12af3369029c13738ad6c40cc7a345d7d81834eca72"
       },
       {
         "path": "templates/lib/memory-protocol.md",
@@ -325,5 +325,5 @@
       }
     ]
   },
-  "signature": "iuNdrUAvCEsJrxokWl6qDVTsiQJb9/v+oSUREgL2dkMEEzslnKnzYH144Cxg/qxpNZqocyHqvsH2A8I1Eu2wCQ=="
+  "signature": "2ltA45AgleqbKopq4ritI5XTO7YtiM/vDWxo6fNIFBYrlz+sz9ZAFSxyNOEN3KYs8uwlgmef1I1sb1wvMIgxAw=="
 }

package/README.md

@@ -106,6 +106,26 @@ ARCHITECTURE → IMPLEMENTATION →  CODE   →   QE    →  FLEET QE
 # Full protocols + 6 extra skills, up to 7 fleet QE agents
 ```
 
+### Advisory micro-recall at two decision points (v1.5.9, staged)
+
+The workflow makes one bounded decision-local recall attempt immediately before the live Step 3
+ADR-alternative choice and one immediately before the live Step 6 plan-route choice. Each attempt
+asks for at most three lessons, uses a decision-specific lesson-bandit context, has a 15-second
+whole-attempt ceiling, and is never retried. The Step 6 Codex-to-Claude fallback reuses the same
+snapshot instead of recalling again.
+
+This is strictly advisory. Empty output, timeout, command/parse/transport failure, an unwritable
+receipt, or an unestablished application probe leaves the original stage prompt, dispatch count,
+result, and verdict unchanged. There is no hard gate or runtime effectiveness threshold.
+
+The append-only evidence lives at
+`features/<slug>/.fa-state/decision-recall.jsonl`: versioned `entered`, `recalled`, `applied`, and
+optional `owner-label` rows. Post-hoc analysis can derive `receipted / eligible`, outcome counts,
+`applied / selected`, owner-label coverage, repeat-hit numerator/denominator, irrelevant injections,
+and explicit uncounted/unknown populations. The motivating timing observation remains external
+`[SRC], n=1`; the required book queries were silent on retrieval timing, so this instrumentation is
+a falsifiable hypothesis, not a claim that decision-point recall is needed or effective here.
+
 ### The K2 plan gate runs on ANY repo, not just JS/TS ones (v1.5.0)
 
 Between Step 6 and Step 7 the pipeline runs a machine plan-completeness gate (K2). Until v1.5.0 it
@@ -169,7 +189,7 @@ refused BY NAME: `path traversal ('..' segment)`, `degenerate path segment`, `em
 `illegal character '<c>'`, `empty stem after the leading dot`. The old substring traversal test also
 rejected the ordinary filename `foo..bar.ts`; it is a segment test now.
 
-### The Step-8 amendment gate runs a command instead of judging (v1.5.7)
+### The Step-8 amendment gate runs a command instead of judging (v1.5.8)
 
 Every `AM-N` row must resolve to a test found INSIDE the file the row names, and the check is
 `dz amendment-check --slug <slug> --json` rather than a paragraph asking the reviewer to confirm it.
@@ -325,14 +345,17 @@ Workflow({ scriptPath: '.claude/workflows/feature-adr.js',
 ```
 
 Omit the Codex knobs entirely for today's all-Claude behavior. The run result reports
-`plannerUsed` / `coderUsed` / `qeReviewerUsed` / `codexModel` / `modelsUsed` so you can see who did what.
-
-**Live model visibility in `/workflows`:** each stage's agent label is decorated with its *resolved*
-model — e.g. `adr · codex:gpt-5.5:xhigh`, `plan · opus` — so you see which model actually ran a stage in
-the live progress tree, not just in the final report. This matters because a Codex stage's auto
-model-badge shows the `codex:codex-rescue` Claude wrapper (the session model), never `codex`; the label
-text is the honest signal. A Claude fallback appears as its own distinct node (never mislabeled as Codex),
-and a routing-off run adds no suffix (byte-identical to today).
+`plannerUsed` / `coderUsed` / `qeReviewerUsed` / `codexModel` / `modelsUsed` as a legacy routing
+summary. `dispatchOutcomes` is the authoritative who-did-what ledger: it contains only settled
+attempts, never pre-dispatch intent.
+
+**Live model visibility in `/workflows`:** each stage prints a two-phase line. `▸ ... · intent`
+appears before the target model starts and names the resolved model and selection reason;
+`◆ ... · outcome: ...` appears only after that attempt settles. Only the latter enters `dispatchOutcomes`.
+This matters because a Codex stage's auto
+model-badge shows the `codex:codex-rescue` Claude wrapper (the session model), never `codex`; the
+two-phase lines are the honest signal. A Claude fallback appears as its own distinct attempt (never
+mislabeled as Codex), and a routing-off intent explicitly says `routing not requested`.
 
 ### Per-stage model routing — `args.models`
 
@@ -1113,6 +1136,24 @@ deliberately excluded — "skeleton first" is nonsense there.
 
 ## Status
 
+`1.5.10` — **staged, not published: every finished phase reports to the 📐 live panel, whatever the
+checkpoint does.** The packaged workflow's `withCheckpoint` computes the next phase label from STAGE
+COMPLETION alone, before any checkpoint branch, so `args.checkpoints:false`, an oversize or
+unserializable result, a stage with no declared artifact, and a refused persist predicate all still
+move the panel. On the common path the `dz statusline --fa-record` command RIDES the existing
+ckpt-write agent — **zero new agents** — joined by `;`, never `&&`: with `&&`, a checkpoint write
+that legitimately refuses short-circuits the phase report away while the workflow has already
+recorded that it ran, and the panel silently stops on a run that is still progressing. Only where no
+checkpoint agent is dispatched at all does the stage spend one extra effort-low `fa-phase:<stage>`
+dispatch, announced in the log. A dead or partial stage reports nothing — the panel must never claim
+progress a stage did not make. Requires `@dzhechkov/harness-cli >= 0.8.11` for the `--tier` flag and
+the second-line panel; the two workflow twins stay byte-identical (`gen-loop-blobs --check`).
+
+`1.5.9` — **staged, not published: advisory decision-point micro-recall.** Step 3 ADR selection and
+Step 6 plan routing each make one top-3, 15-second, no-retry attempt inside the live checkpoint thunk.
+All recall/receipt/probe failures preserve the original dispatch. Versioned `.fa-state` receipts make
+coverage and repeat-related outcomes countable offline; no threshold controls the workflow.
+
 `1.5.4` — **Step 5 now asks how the shipped feature will be watched.** The architecture artifact must
 carry a section headed exactly `Observability` answering what the feature logs, what it counts, what a
 failure looks like from outside, and who would notice. **"Nothing to observe" is a complete answer** —
@@ -1160,3 +1201,13 @@ Also in this release, both halves of the K2 plan-completeness gate that field us
   installed in the workspace was never found (`NOT-ESTABLISHED`, exit 3, the coding step never ran).
   New `args.workspace` pins it, the shipped call site passes it, each candidate is now labelled in the
   audit line, and a `K2_GATE_NOTE` fires when the two collapse onto one path.
+
+## Двухфазная строка диспатча (шаблон воркфлоу)
+
+Шаблон `.claude/workflows/feature-adr.js` печатает две разные строки без флага: намерение
+`▸ <стадия> · <модель> · <причина выбора> · intent` непосредственно до запуска модели и итог
+`◆ <стадия> · <модель> · outcome: <исход>` после окончательного состояния той же ступени.
+Даже долгий или бросивший исключение запуск заранее виден человеку; при этом только итог попадает в
+`dispatchOutcomes` отчёта. Причина отказа остаётся у outcome отказавшей ступени, а intent следующего
+fallback получает нейтральную причину `fallback-rung`. Регион `stage-line` принадлежит генератору
+`gen-loop-blobs` и не правится руками.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dzhechkov/skills-feature-adr",
-  "version": "1.5.7",
+  "version": "1.5.10",
   "description": "Adaptive Feature Development skill pack for Claude Code — 11-step pipeline with Complexity Router (S/M/L/XL), ADR-driven architecture, 15 agentic-qe skills, multi-agent fleet QE. Supports --full-qe, --full-qe-extended, --with-learning, and --knowledge-extractor modes.",
   "bin": {
     "skills-feature-adr": "./bin/cli.js"
@@ -42,12 +42,12 @@
   },
   "repository": {
     "type": "git",
-    "url": "https://github.com/djd1m/dz-harness-hub.git",
+    "url": "git+https://github.com/djd1m/dz-harness.git",
     "directory": "packages/@dzhechkov/skills-feature-adr"
   },
-  "homepage": "https://github.com/djd1m/dz-skill-bundles/blob/main/docs/feature-adr-team-onboarding.md",
+  "homepage": "https://github.com/djd1m/dz-harness/tree/main/packages/@dzhechkov/skills-feature-adr#readme",
   "bugs": {
-    "url": "https://github.com/djd1m/dz-skill-bundles/issues"
+    "url": "https://github.com/djd1m/dz-harness/issues"
   },
   "peerDependencies": {
     "@dzhechkov/keysarium-core": "^1.0.0"

package/sbom.json

@@ -35,7 +35,7 @@
       "hashes": [
         {
           "alg": "SHA-256",
-          "content": "4ab808507be5c64cfa7b74ef3c186145d0654cd9c2fad86229685edaac6edb10"
+          "content": "b1dbcb7b1f0f3d95bdda9f9568f65e1f78b306b2cb64e42979b1981aeadc6047"
         }
       ]
     },
@@ -69,7 +69,7 @@
         },
         {
           "name": "dz:canonical-json-sha256-v2",
-          "value": "1efad8edf817286284ef35578e3b5046205350603b7e9cb9b979993a69f85c8a"
+          "value": "e376fe73743953ad7f0b7525e22f815ea949450fe7ea784f89d1e61bcc62ce6f"
         }
       ]
     },
@@ -629,7 +629,7 @@
       "hashes": [
         {
           "alg": "SHA-256",
-          "content": "630eb9047258ad0333082f407cd34522e4c278650f22ef6dba1ef897ec5cce71"
+          "content": "cd2d4e05d1b61be5485c9836abdebdb00b5f4085a14f3c71126cc45d4e08fe3b"
         }
       ]
     },
@@ -789,7 +789,7 @@
       "hashes": [
         {
           "alg": "SHA-256",
-          "content": "f5454faf9cca12a3cbef5444a3fe586823bfe2a164ab391c9589ed206a0b9b9f"
+          "content": "ef6a119466e504307116b12af3369029c13738ad6c40cc7a345d7d81834eca72"
         }
       ]
     },

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

@@ -180,7 +180,21 @@ if (adrFiles.length === 0 && TIER_REQUIRES_ADR) {
     const adr = readFileSync(join(adrDir, f), 'utf-8');
     const confIdx = adr.search(/^##+\s*Confirmation/mi);
     if (confIdx < 0) { failures.push(`C2: ${safe(f)} has no Confirmation section`); continue; }
-    const conf = adr.slice(confIdx);
+    // The section ENDS at the next heading of the same or higher level — it does not run to EOF.
+    // Slicing to EOF swallowed every later section, so a `Links` entry citing an existing test as
+    // PRECEDENT was read as this ADR's own Confirmation and demanded of the plan (measured
+    // 2026-08-31 on features/finding-identity-closure: reqe.test.ts, cited under
+    // "Implementation precedent", failed C2 while the real Confirmation test was named correctly).
+    // Deeper subsections stay inside: a Confirmation with ### children is one section.
+    const rest = adr.slice(confIdx);
+    const confLevel = (rest.match(/^(#+)/) || ['', '##'])[1].length;
+    // Search AFTER the Confirmation heading's own line — searching from the heading itself matches
+    // it and collapses the section to nothing, which turns a scoping fix into a gate that reports
+    // "Confirmation names no test file paths" for every ADR (caught by running it).
+    const bodyStart = rest.indexOf('\n') + 1;
+    const afterHeading = rest.slice(bodyStart);
+    const nextHeading = afterHeading.search(new RegExp('^#{1,' + confLevel + '}[^#]', 'm'));
+    const conf = nextHeading < 0 ? rest : rest.slice(0, bodyStart + nextHeading);
     const paths = extractCandidatePaths(conf).filter(isTestPath);
     // UNKNOWN ECOSYSTEM STAYS A FAILURE, never a WARN: a gate that downgrades itself on the one
     // repo it cannot read is a gate that is off exactly where it is needed. The remedy is named