@dzhechkov/skills-feature-adr 1.5.14 → 1.5.16

package/.dz-manifest.json

@@ -13,7 +13,7 @@
       },
       {
         "path": "README.md",
-        "sha256": "8c96e82b41fb8479befb56797a367b3cc2119cc5b022b18fdd18f129ef8cd0f0"
+        "sha256": "a76e2b71dd2598d4d6789ee00ce99791d4e4927466f4800e5637c4bbbade859e"
       },
       {
         "path": "bin/cli.js",
@@ -25,7 +25,7 @@
       },
       {
         "path": "package.json",
-        "sha256": "0cdd048a5aacd52294f72b5903b5a94c049ad61680dbcac532d5cb3fbd45c736"
+        "sha256": "d9af637b1b430a77811424de145ff5a72eceff10b7a583413affa4899c877b8e"
       },
       {
         "path": "src/cli.js",
@@ -113,7 +113,7 @@
       },
       {
         "path": "templates/.claude/skills/feature-adr/SKILL.md",
-        "sha256": "67eb730c815e6b8f9b9b61084c67ceb85440548f00b21f52187d16e81e3d7af8"
+        "sha256": "28c265603481f976a52ea4c627e11194f3c0283801ea93d02cbb9f4248b43c68"
       },
       {
         "path": "templates/.claude/skills/feature-adr/examples/sample-feature-output.md",
@@ -137,7 +137,7 @@
       },
       {
         "path": "templates/.claude/skills/feature-adr/modules/03.5-ideation-swarm.md",
-        "sha256": "d48a8d6eebf9760cc8f1a4f19df0e6afc31fcc1284b5eacfb604ad8ced6a0b53"
+        "sha256": "b6e505083c1b8bc92243379b72ff4667b5b91ef65fd9c2ef7407129018b3e56b"
       },
       {
         "path": "templates/.claude/skills/feature-adr/modules/04-ddd.md",
@@ -149,15 +149,15 @@
       },
       {
         "path": "templates/.claude/skills/feature-adr/modules/06-implementation-plan.md",
-        "sha256": "5c8d4c79d5329702b8c75b9afb36ae335aa63c99e74045c0afa98e12658ee975"
+        "sha256": "d7a2a4e56b24451da234b1ac4ef440ba9b0370617e1c0cde8ad5f3d575a53209"
       },
       {
         "path": "templates/.claude/skills/feature-adr/modules/07-code.md",
-        "sha256": "fb054591e86d55cee184eab96b5f0440053ada8fa9edf619e4a66ec5ac371587"
+        "sha256": "db79f8d026cc47edd1e5d2f30d0e1455c55c570dd022d549d440985a3e5940a5"
       },
       {
         "path": "templates/.claude/skills/feature-adr/modules/08-qe.md",
-        "sha256": "5355e2b36ab13b6acb65abe5b206685915ef2b08191b4a3130574620012b9135"
+        "sha256": "4aa7ef1dea08b8d1995d968a317da5d36a4859ec299637bdc60170cf577c87af"
       },
       {
         "path": "templates/.claude/skills/feature-adr/modules/09-fleet-qe.md",
@@ -247,9 +247,17 @@
         "path": "templates/.claude/skills/feature-adr/references/qe-checklist.md",
         "sha256": "238d8896996dc53559f58b24aa7eca966cc8845c3b9dda6d982c717c657b91e4"
       },
+      {
+        "path": "templates/.claude/skills/feature-adr/scripts/build-coder-context.mjs",
+        "sha256": "19c3991bfb5e88205c9ff6d4d44037c136a190581bab199d3928196e4616fe15"
+      },
       {
         "path": "templates/.claude/skills/feature-adr/scripts/check-plan-completeness.mjs",
-        "sha256": "eb77822f121ade10bd6265b0f0145ec38507a07d2cb72ba5fa8336c962096bda"
+        "sha256": "8b93949ce4f671d932c5389050db3a3e2750efcbed69681d69f392ccf4d2a168"
+      },
+      {
+        "path": "templates/.claude/skills/feature-adr/scripts/check-review-convergence.mjs",
+        "sha256": "80f9691b8e94bf310461aeaaaa23af6e336d41d0962fdf137737639655cbdeb8"
       },
       {
         "path": "templates/.claude/skills/feature-adr/scripts/markdown-masker.mjs",
@@ -317,7 +325,7 @@
       },
       {
         "path": "templates/.claude/workflows/feature-adr.js",
-        "sha256": "6d1bb93be6fae296281ac8f9fc2f266e5f09336cf6e183912fab5ff3bd0d3fd8"
+        "sha256": "6f9e6205c8f78bef8086603bf0efe8099011a2cc273d786b8404bd77af565354"
       },
       {
         "path": "templates/lib/memory-protocol.md",
@@ -329,5 +337,5 @@
       }
     ]
   },
-  "signature": "+DKyJg37w6aHqhg/UhCpQ+y+w/e66HEEr9hgOv/TttSIMc6TokGEbvJpxEw2pdu19Q0SHlA/o6pSucM+h3KEDw=="
+  "signature": "nV5vsSwCCTR5hUAMHmxpGPe3DoZoRQJsnAdqqm4gO0OPm1GHMWBx5AZhJEC1jzUugamIpkJEPtWCsD6d+e0oAg=="
 }

package/README.md

@@ -1,5 +1,9 @@
 # @dzhechkov/skills-feature-adr
 
+Current package version: `1.5.16`. <!-- dz:version -->
+
+Site: https://aicoding.space · Source: https://github.com/djd1m/dz-harness/tree/main/packages/@dzhechkov/skills-feature-adr
+
 **Spec-Driven Development pipeline for AI coding agents (Claude Code, Codex, …)**
 
 An 11-step, complexity-routed pipeline that makes an AI coding agent build a feature the way a
@@ -37,6 +41,21 @@ npx @dzhechkov/skills-feature-adr init
 
 After installation, open Claude Code in your project directory and use `/feature-adr`.
 
+Plain usage guidance joins the existing stage writer to `usage --by-stage --project` with explicit FA/
+Wf source selection and observed receipt IDs. It preserves unknown splits/prices, caller estimates and
+separate conservation/inventory/source verification. No billing inference, new ledger or paid replay.
+
+Plain Step 8 bridge guidance now passes current `--round`, `--round-run` and `--task` from the existing
+round receipt with the execution `--project`. Explicit conflicts refuse before reviewer work; the
+bridge's invocation `runId` stays distinct from pipeline identity. Native Workflow QE remains its own
+review path. Historical window correlation is disclosed as lower assurance, without guessed identity.
+
+Step 7 uses the installed `scripts/build-coder-context.mjs` helper to include literal requirements,
+plan tasks and ADR Decision/Confirmation. Workflow reads current inputs before code checkpoint
+lookup; plain coding runs the same helper and reads or embeds its successful `promptBlock`.
+Missing required sections, invalid files and exceeded UTF-8 bounds refuse coding instead of trimming
+the context. Existing decision recall and code-wrapper routing remain in place.
+
 ---
 
 ## What You Get
@@ -1363,3 +1382,39 @@ harness-core's `src/markdown-masker.ts`. It runs without a core build. Amendment
 and K2 share the parser while retaining their existing unclosed-block and indentation policies.
 The four-space indented-code gap remains open for amendment checks and K2; swarm briefs retain their
 existing masking of indented code. Versions are unchanged in this staged change.
+
+### Codex companion for feature-adr
+
+`dz statusline --watch --project "/path/to/worktree" --brain "/path/to/shared-brain"
+--slug "feature-slug" --run-id "stable-run-id"` adds an explicitly launched adjacent terminal
+companion, including Plain runs. Until installed, invoke the worktree-built
+`node packages/@dzhechkov/harness-cli/dist/bin.js statusline --watch ...`. This extends the existing
+command inventory. Canonical feature-adr guidance supplies the quoted producer/observer recipe: record
+a stable run ID and actual tier at the START of each step, then `done` on real completion; recall/teach
+remain scoped to the shared brain. Project run state and brain counts are separate. One slug retains
+one latest run; report freshness is not process liveness and stage position is not passed gates.
+
+The readonly companion requires a dedicated stdout TTY, uses serial 2-second refreshes (0.25–60
+allowed), sanitizes/clips text and handles resize. Below 40x8 it shows a size warning. Ctrl-C/SIGTERM
+exit 0; output failure 1; invalid/piped watch 2. Failed/absent counts and optional values are explicit;
+watch v1 ETA is unavailable and global source inventory omitted. No stdin/raw mode, models, logical
+store writes or automatic terminal/settings changes. Normal SQLite ephemeral WAL/SHM sidecars are
+permitted. One-shot Claude text/JSON/ETA remain unchanged. Codex native footer capability is not
+asserted; parity names manual `dz statusline --watch` access.
+
+
+Review convergence in `/feature-adr` now uses one installed Node gate in Plain and native Workflow.
+Step 3.5 closes before planning; Step 8 closes before completion and delivery, including S tier and
+resumed runs. The host measures current artifact bytes and preserves originating reviewer conditions;
+focused rework includes an explicit author delta/new-risk assessment and independent own-condition
+verification. Serious primary or precision findings remain visible at the round ceiling.
+
+Missing or stale receipts, legacy resume, unavailable reviewers and read-only Codex mode A pause
+with host-driven repair instructions. Parallel native design can require focused review after sibling
+artifacts settle. Clean initial supported review closes without invented conditions or an extra review.
+This is a receipt consistency/freshness gate, not reviewer authentication or semantic proof; existing
+Confirmation, scope, family and budget gates still apply. No automatic repair loop or new CLI command.
+
+Repeated prepare retains all pending paths until verified closure. Actual fallback families bind before dispatch while prior owners remain required. Same-slug QE repair uses current own-reviewer evidence bound to the complete historical checkpoint; original findings/grades remain visible, and failed Confirmation still blocks delivery.
+
+Before fallback, host prepare retains independently written pending receipt findings under the original owner even if that reviewer returned null. Unreconciled pending evidence pauses dispatch for originating-reviewer repair; it cannot be replaced by a clean fallback to obtain closure.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dzhechkov/skills-feature-adr",
-  "version": "1.5.14",
+  "version": "1.5.16",
   "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"
@@ -49,7 +49,7 @@
     "url": "git+https://github.com/djd1m/dz-harness.git",
     "directory": "packages/@dzhechkov/skills-feature-adr"
   },
-  "homepage": "https://github.com/djd1m/dz-harness/tree/main/packages/@dzhechkov/skills-feature-adr#readme",
+  "homepage": "https://aicoding.space",
   "bugs": {
     "url": "https://github.com/djd1m/dz-harness/issues"
   },

package/sbom.json

@@ -35,7 +35,7 @@
       "hashes": [
         {
           "alg": "SHA-256",
-          "content": "8c96e82b41fb8479befb56797a367b3cc2119cc5b022b18fdd18f129ef8cd0f0"
+          "content": "a76e2b71dd2598d4d6789ee00ce99791d4e4927466f4800e5637c4bbbade859e"
         }
       ]
     },
@@ -69,7 +69,7 @@
         },
         {
           "name": "dz:canonical-json-sha256-v2",
-          "value": "0cdd048a5aacd52294f72b5903b5a94c049ad61680dbcac532d5cb3fbd45c736"
+          "value": "d9af637b1b430a77811424de145ff5a72eceff10b7a583413affa4899c877b8e"
         }
       ]
     },
@@ -289,7 +289,7 @@
       "hashes": [
         {
           "alg": "SHA-256",
-          "content": "67eb730c815e6b8f9b9b61084c67ceb85440548f00b21f52187d16e81e3d7af8"
+          "content": "28c265603481f976a52ea4c627e11194f3c0283801ea93d02cbb9f4248b43c68"
         }
       ]
     },
@@ -349,7 +349,7 @@
       "hashes": [
         {
           "alg": "SHA-256",
-          "content": "d48a8d6eebf9760cc8f1a4f19df0e6afc31fcc1284b5eacfb604ad8ced6a0b53"
+          "content": "b6e505083c1b8bc92243379b72ff4667b5b91ef65fd9c2ef7407129018b3e56b"
         }
       ]
     },
@@ -379,7 +379,7 @@
       "hashes": [
         {
           "alg": "SHA-256",
-          "content": "5c8d4c79d5329702b8c75b9afb36ae335aa63c99e74045c0afa98e12658ee975"
+          "content": "d7a2a4e56b24451da234b1ac4ef440ba9b0370617e1c0cde8ad5f3d575a53209"
         }
       ]
     },
@@ -389,7 +389,7 @@
       "hashes": [
         {
           "alg": "SHA-256",
-          "content": "fb054591e86d55cee184eab96b5f0440053ada8fa9edf619e4a66ec5ac371587"
+          "content": "db79f8d026cc47edd1e5d2f30d0e1455c55c570dd022d549d440985a3e5940a5"
         }
       ]
     },
@@ -399,7 +399,7 @@
       "hashes": [
         {
           "alg": "SHA-256",
-          "content": "5355e2b36ab13b6acb65abe5b206685915ef2b08191b4a3130574620012b9135"
+          "content": "4aa7ef1dea08b8d1995d968a317da5d36a4859ec299637bdc60170cf577c87af"
         }
       ]
     },
@@ -623,13 +623,33 @@
         }
       ]
     },
+    {
+      "type": "file",
+      "name": "templates/.claude/skills/feature-adr/scripts/build-coder-context.mjs",
+      "hashes": [
+        {
+          "alg": "SHA-256",
+          "content": "19c3991bfb5e88205c9ff6d4d44037c136a190581bab199d3928196e4616fe15"
+        }
+      ]
+    },
     {
       "type": "file",
       "name": "templates/.claude/skills/feature-adr/scripts/check-plan-completeness.mjs",
       "hashes": [
         {
           "alg": "SHA-256",
-          "content": "eb77822f121ade10bd6265b0f0145ec38507a07d2cb72ba5fa8336c962096bda"
+          "content": "8b93949ce4f671d932c5389050db3a3e2750efcbed69681d69f392ccf4d2a168"
+        }
+      ]
+    },
+    {
+      "type": "file",
+      "name": "templates/.claude/skills/feature-adr/scripts/check-review-convergence.mjs",
+      "hashes": [
+        {
+          "alg": "SHA-256",
+          "content": "80f9691b8e94bf310461aeaaaa23af6e336d41d0962fdf137737639655cbdeb8"
         }
       ]
     },
@@ -799,7 +819,7 @@
       "hashes": [
         {
           "alg": "SHA-256",
-          "content": "6d1bb93be6fae296281ac8f9fc2f266e5f09336cf6e183912fab5ff3bd0d3fd8"
+          "content": "6f9e6205c8f78bef8086603bf0efe8099011a2cc273d786b8404bd77af565354"
         }
       ]
     },

package/templates/.claude/skills/feature-adr/SKILL.md

@@ -562,13 +562,91 @@ only the statusline:
 
 **Record the panel at the START of every step, not only at Steps 0/8/9.** The panel shows the last step
 that reported; a pipeline that reports three times per run shows a stale step for most of its life. Emit
-`dz statusline --fa-record --slug <slug> --step "<Step N Name>" --recalled <n> --stored <n>` as the first
+`dz statusline --fa-record --project "<worktree>" --slug "<slug>" --run-id "<stable-run-id>" --tier M --step "<Step N Name>" --recalled <n> --stored <n>` as the first
 action of each step. The recall/teach counts only change at Steps 0/8/9; the *step label* changes at every
 one of them.
 
 *Honesty note:* the panel is live only insofar as the pipeline records state — it reflects what the
 pipeline actually did with the loop (recalls that ran, stores that landed), not an aspirational count.
 
+### Plain observed usage receipts
+
+Use the existing witnessed writer for usage you actually observed. At a real stage boundary,
+capture the execution project, stable run/task, verbatim stage, actual model/family/role, attempt,
+tier/mode and source window/IDs available to this host. Missing fields remain null with their reason;
+do not infer input/cache from total, price from a model family, or tokens from invocation budgets.
+
+```bash
+dz feature-adr-record --kind ledger --stage "$CURRENT_STAGE" --project "$EXECUTION_PROJECT" \
+  --row "$OBSERVED_STAGE_ROW_JSON" --rollout-id "$ACTUAL_SESSION_ID" --turn-id "$ACTUAL_TURN_ID" --json
+dz usage --by-stage --project "$EXECUTION_PROJECT" --source fa-ledger --run "$STABLE_RUN_ID" --json
+```
+
+`OBSERVED_STAGE_ROW_JSON` is real host metadata: `runId`, `taskId`, `stage`, `model`, `family`, `role`,
+`attempt`, `tier`, `mode`, `tokens`/dimensions when observed, and optional separate `estimate` with
+tokens/costUsd/method/source/capturedAt. Omit selectors not known; window/cwd/model-only correlation
+is labelled legacy-window and cannot claim exact source verification. Source roots can be named with
+`--codex-sessions`. Exact IDs are validated against existing receipts; no new IDs or recall/teach occur.
+The source receipt subset is captured once; later source append cannot enlarge the old row.
+Captured payload integrity and every pricing-bearing dimension must match the original scoped source.
+A reported monetary amount belongs to one observation, not each expanded token receipt. Preserve an
+actual observation ID/scope/basis in optional `reportedCostObservation: { id, scope, basis }` within
+`--row` when known; otherwise a captured source scope supplies a stable identity and unrelated money
+attribution stays unavailable. Reimports of the same observation count once; conflicting amounts are
+diagnosed. Missing money differs from zero. Exports must avoid every selected authoritative source,
+including custom run directories and symlink aliases. Invalid Claude counters retain nulls/diagnostics;
+a declared invalid total cannot derive a replacement, and accounting validity does not rewrite the
+actual generation outcome.
+
+For Wf, use `--source workflow-budget --run <id>` and optional `--run-dir <dir>` for its existing
+budget/trace/state. Auto source collisions require an explicit source; joined Wf summary projections
+never add another cost. Preserve reported total basis and cache/reasoning subsets. Wf budget.spent
+counts dispatch units; native Workflow's existing budget delta is output-only. Neither is raw total.
+
+Reports separate conservation, expected inventory and independent amount verification. Without
+a same-scope witness, verified totals are null even when reported values conserve. Unknown rates or
+split keep primary estimated USD null; static family estimates, provider-reported USD and caller
+pre-run estimates are separate, never current exact prices or billed amounts. Billing remains unobserved.
+
+### Codex companion terminal (Plain included)
+
+Open an adjacent terminal or a manual tmux split and launch the observer explicitly. Codex does not
+have a dz native command-provider footer. Keep the producer's project, slug and stable run ID equal to
+the observer's; use the actual complexity tier at the START of every active step. Brain is the shared
+learning store for recall/teach, while project is the worktree containing run slots and branch.
+
+```bash
+# Set these to your actual absolute paths. Use the worktree build until the change is installed.
+PANEL_CLI="/path/to/worktree/packages/@dzhechkov/harness-cli/dist/bin.js"
+PANEL_PROJECT="/path/to/worktree"
+PANEL_BRAIN="/path/to/canonical-brain"
+PANEL_SLUG="feature-slug"
+PANEL_RUN="feature-20261002-1"  # choose once per invocation, retain at every step
+node "$PANEL_CLI" statusline --watch --project "$PANEL_PROJECT" --brain "$PANEL_BRAIN" \
+  --slug "$PANEL_SLUG" --run-id "$PANEL_RUN" --interval 2
+# In the producer terminal, at the START of each real step (example: tier M):
+node "$PANEL_CLI" statusline --fa-record --project "$PANEL_PROJECT" --slug "$PANEL_SLUG" \
+  --run-id "$PANEL_RUN" --tier M --step "Step 7 Code" --recalled 3 --stored 0
+# Only after the run actually completes; this is not a claim that QE passed:
+node "$PANEL_CLI" statusline --fa-record --project "$PANEL_PROJECT" --slug "$PANEL_SLUG" \
+  --run-id "$PANEL_RUN" --tier M --step "done" --recalled 3 --stored 0
+```
+
+Use `dz recall ... --project "$PANEL_BRAIN"` and `dz teach ... --project "$PANEL_BRAIN"` for actual
+learning. Supply measured cumulative counters, not the example numbers. The observer counts its brain
+source directly; the slot's producer pool is not a shared-brain inventory. One slug holds one latest
+run, so a replacement makes an exact old selection missing. No selectors means visibly automatic
+selection. Freshness measures producer-report age, not process liveness: fresh <30 minutes, stale
+30–<90, expired >=90; completed remains completed. Stage position is not completed gates.
+
+Watch v1 displays ETA unavailable, unknown optional values and unavailable failed/absent learning
+sources, and omits ambiguous global source inventory. It uses escaped ASCII text, a dedicated stdout
+TTY, 0.25–60 second intervals (default 2), and a size warning below 40 columns/8 rows. Ctrl-C/SIGTERM
+exit 0; output failures exit 1; piped output and watch+JSON/install/record combinations exit 2.
+Observation never reads stdin, runs models or writes logical store state. SQLite-managed ephemeral
+WAL/SHM files are permitted; no application locks, repair or schema changes occur. One-shot Claude
+statusline/JSON and its ETA keep their existing behavior. Do not start a terminal automatically.
+
 ### What changes with `--full-qe`
 
 Full agentic-qe protocols for the same 9 core skills. No new agents, just deeper methodology.

package/templates/.claude/skills/feature-adr/modules/03.5-ideation-swarm.md

@@ -27,6 +27,135 @@ sonnet (analytical quality assessment — multiple parallel agents)
 
 ## Protocol
 
+## Review convergence gate (Plain and native Workflow)
+
+Review follows **initial review → host rework → focused verification → closure**, or explicit owner
+escalation. A grade/GO label does not establish closure. Run the same installed Node gate before
+planning (phase `ideation`) and before Step-8 completion/delivery (phase `qe`), including resume.
+
+The host prepares a measured artifact snapshot BEFORE independent review. Resolve the executable
+from this installed skill's `scripts/check-review-convergence.mjs`; do not use a scratch replacement.
+For example, from the execution project, using the actual originating role/family:
+
+```bash
+node "$FEATURE_ADR_SKILL/scripts/check-review-convergence.mjs" prepare \
+  --repo "$EXECUTION_PROJECT" --feature "features/$FEATURE_SLUG" --phase ideation \
+  --reviewers '[{"id":"qcsd-quality","family":"owner-exception"},{"id":"qcsd-risk","family":"owner-exception"},{"id":"qcsd-testability","family":"owner-exception"}]'
+node "$FEATURE_ADR_SKILL/scripts/check-review-convergence.mjs" evaluate \
+  --repo "$EXECUTION_PROJECT" --feature "features/$FEATURE_SLUG" --phase ideation
+```
+
+For QE use `--phase qe` and the actual `qe-primary` reviewer, plus `qe-precision` when configured.
+`family` is `codex`, `claude`, or an explicitly authorized `owner-exception`. Existing family/routing
+policy remains binding; this receipt does not authorize an exception. Only the host calls `prepare`.
+It retains originating reviewer roles and prior condition meanings in the existing feature checkpoint
+`.fa-state/review-convergence-<phase>-host.json`; neither the latest report nor an empty request array
+can replace that lineage. Do not edit/delete host lineage to obtain a clean bootstrap. A new nonce is
+issued when measured bytes/path membership change; repeated preparation cannot remove conditions. Pending changed paths accumulate across every prepare, including path additions/deletions, until an established closure; failed/refused evaluations never clear them.
+
+The snapshot measures requirements, every direct ADR, architecture, and other available design
+inputs. QE also measures the plan, ideation report, every declared target, and host-discovered Git
+changes/additions/deletions against `.fa-state/base-ref` (HEAD when absent). Receipt/checkpoint files,
+QE report and generated `architecture/map.json` are outputs excluded to avoid circular hashes.
+Explicit planned deletions carry a null digest. Traversal, symlinks and non-files refuse. The host
+must include relevant unchanged dependencies in declared targets; hashing cannot discover semantic
+dependencies. Parallel Workflow design may change after ideation review: that stale review pauses
+before planning and needs focused review of the settled snapshot.
+
+All three QCSD core roles remain originating reviewers. The coordinator does not manufacture their
+receipts from grades or report prose. The JSON example below shows one entry; include all three
+actual roles in `reviews`, with their actual families. Each independent reviewer writes its OWN
+entry, preserving other reviewer entries and the actual
+author handoff, in `.fa-state/review-convergence-<phase>-review.json`. A genuinely clean initial
+review needs no invented condition or extra review. Its complete receipt shape is:
+
+```json
+{
+  "schema": "fa-review-convergence-1", "phase": "ideation",
+  "nonce": "<copy host snapshot nonce>", "revision": "<copy host snapshot revision>",
+  "author": null,
+  "reviews": [{
+    "reviewer": "qcsd-quality", "family": "owner-exception", "independent": true, "verdict": "clean",
+    "conditions": [], "verifications": [],
+    "newRisks": {"assessment": "none identified after complete scope review", "evidence": "<actual review evidence>", "conditions": []},
+    "authorAssessmentChecked": false, "deltaVerification": null
+  }]
+}
+```
+
+`verdict` is `clean`, `conditional`, or `no-go`. Conditions have closed fields
+`{id, owner, severity, classification, requirement, scope, evidence}`: stable unique ID, originating
+role ID, BLOCKER/CRITICAL/HIGH/WARNING/SUGGESTION, structural/wording, exact acceptance meaning,
+nonempty repo-relative scope paths, and original evidence. Carry every prior own condition unchanged
+on every pass. Reviewer verifications have closed fields
+`{id, revision, classification, evidence, implementationVerified}`. Only the originating independent
+role can verify its own condition at the current revision; author/lead/scribe assertions cannot.
+
+Rework requires the actual author object
+`{addressed, changedScope, classification, delta, evidence, newRisks}`. Addressed IDs name prior
+conditions; changedScope includes ALL host-measured changes and affected dependencies. Delta/evidence
+explain the actual fix. Both author and reviewer `newRisks` require explicit assessment/evidence and a
+conditions array, including an explicit none-identified assessment when empty. The reviewer must set
+`authorAssessmentChecked:true` and supply independent
+`deltaVerification:{classification,evidence,implementationVerified}`. Structural changes affect
+behavior, contracts, safeguards, architecture or acceptance meaning and require affected implementation
+and test verification. Wording changes affect expression only; the independent reviewer checks that
+classification, so an author's wording label cannot weaken structural verification.
+
+Focused scope is outstanding conditions plus actual changes and affected dependencies. New serious
+risks always expand that scope. Retain ALL conditions and serious primary/precision findings until
+own-reviewer verification; a token/round ceiling escalates unresolved risk, never approves it.
+
+Gate exits: 0 with `prepared` (prepare only) or `closed` (evaluate only); 1 `unresolved`; 3
+`not-established`. Inspect the structured reasons/unresolved IDs. Missing executable/report, malformed
+or contradictory output, foreign/duplicate/omitted conditions, stale phase/nonce/manifest or unavailable
+reviewer refuses. Native Workflow strictly checks stdout AND exit before planning and before
+completion/delivery/success tags. Supported native/Mode-B/fallback/precision reviewers receive this
+contract; the read-only Codex mode-A route cannot accept it and pauses for a supported independent
+review. A scribe never creates reviewer evidence from grade. Historical resume without this contract
+needs fresh evidence; resume rechecks bytes and every configured route, including unwitnessed precision.
+
+Host prepare first reads the existing reviewer receipt, including valid partial own entries written
+before an agent/transport failure. It preserves independently written conditions under their original
+role/family before binding any actual fallback. This imports findings, never closure or author/scribe
+claims. A stale receipt cannot originate new host conditions; known prior meanings remain immutable.
+`pending-reviewer-receipt-needs-origin-review` pauses before native fallback dispatch when pending
+evidence cannot be reconciled. Keep the original receipt and host lineage. Have its originating
+reviewer repair malformed/foreign fields or refresh unknown stale own findings at the unchanged
+host identity/current snapshot. Repeat prepare for the selected actual base-role families, complete
+the returned full reviewer roster with actual own verification, then evaluate and resume the same
+slug. No receipt/lineage deletion or relabeling is a recovery action. The existing QE checkpoint
+validator rejects a paused non-QE result, so same-slug resume re-enters only that reviewer stage;
+unrelated coder checkpoints remain eligible for reuse.
+
+Bind the actual fallback family with host prepare BEFORE reviewer dispatch. An unused role may change family; once review evidence originated, its role/family and prior conditions remain required, and the new family receives a distinct `<base-id>:<family>` role. Reviewers read the returned full roster and never relabel old ownership.
+
+On refusal, the host settles artifacts, calls prepare with the selected actual base-role families, supplies
+the author handoff, requests focused own-condition verification, then evaluates and resumes the same
+slug. This is host-driven repair, not an automatic repair loop. Existing Confirmation, amendment,
+scope, testing, independent-family and budget gates remain conjunctive. This gate establishes receipt
+consistency and current artifact binding, not semantic truth or authenticated reviewer identity.
+
+For a same-slug QE resume blocked by historical serious findings, read-only mode A, or an
+unwitnessed precision append, preserve the complete original checkpoint, findings and grades.
+Prepare returns `checkpointDigest`: SHA-256 of `JSON.stringify` of the latest `qe` result in
+`.fa-state/checkpoints.jsonl`. Each actual originating reviewer supplies optional closed-field
+`checkpointVerification:{checkpointDigest,evidence,supported:true,route,findings,reportDigest}`
+in its own review entry, in addition to the ordinary current-revision independent verification.
+`route` is native/mode-b/fallback and evidence describes the actual supported focused review;
+mode A, author/scribe flags, or the old grade cannot establish this proof. `findings` maps EVERY
+original serious gap with `{digest,conditionId}`, where digest is SHA-256(JSON.stringify(gap))
+and conditionId names that reviewer's preserved serious condition with its current structural
+implementation verification. Both primary and precision origins must verify their own findings.
+Use `reportDigest:null` normally; an unwitnessed precision append requires that originating
+precision reviewer to verify the actual complete `08_qe_report.md` and supply its SHA-256.
+The report must contain Primary QE pass, Precision QE pass, and Combined Step-8 grade sections.
+Then evaluate with the same phase/repo/feature and re-invoke the same slug. Only a closed gate
+with complete checkpoint binding can reconcile historical refusals on an actual resumed QE stage;
+live findings, changed checkpoints/artifacts and a failed Confirmation gate still block delivery.
+This procedure runs no coder or automatic repair loop, and retains the historical result for audit.
+
+
 ### 1. Flag Detection (MANDATORY)
 
 Scan feature requirements + ADR decisions and SET these flags:

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

@@ -235,6 +235,16 @@ C2 recognises JS/TS, pytest, Go, Rust, JVM and .NET test paths, extensible per p
 
 Never proceed on a non-zero exit, and never treat empty output as a pass — the last line
 (`K2 plan-completeness: PASS|FAIL|NOT-ESTABLISHED`) is the verdict, and its absence is not one.
+
+**Where an id counts (the default since 2026-09-27, owner decision).** C1 and C8 read the plan's
+TASK LINES only: a heading, a list item or a table row. An `ADR-<n>` or `FR-<n>` that appears only
+in a prose paragraph, a fenced code block (the SPARC-GOAP ```yaml goal state included), an HTML
+comment, the `## Amendments` section or the `EXPECTED_CODE_TARGETS:` block is a mention, not a task,
+and the gate FAILs it with `(cited only outside task lines)`. Write the id on the FIRST line of the
+task that implements it: a wrapped continuation line of a list item is not read either. Measured on the archive when the default changed: 56 of 102 plans that had
+passed would fail this reader, so a plan written before that date may be red on a re-check — move
+the citation onto a task line, or re-check that one plan with `--no-require-task-lines` and say so
+in the checkpoint banner.
 What it checks: C1 every ADR **decision** (a `# ADR-NNN` / `## ADR-NNN` heading INSIDE the file, not
 just the filename prefix — a file with several headings owes several plan citations) has a plan task
 citing it · C2 every ADR Confirmation test path is named in the plan · C3 the `EXPECTED_CODE_TARGETS:`

package/templates/.claude/skills/feature-adr/modules/07-code.md

@@ -26,6 +26,35 @@ opus (complex code generation)
 
 ### 1. Pre-Implementation Checklist
 
+### Current literal context (plain and delegated coding)
+
+Before coding or delegating, run the installed helper beside this module. Set `CONTEXT_HELPER` to
+the absolute `scripts/build-coder-context.mjs` path of the skill installation you are reading;
+set `FEATURE_DIR` to the absolute target `features/<slug>` directory and use the actual tier:
+
+```bash
+node "$CONTEXT_HELPER" "$FEATURE_DIR" --tier=M
+```
+
+The command emits exactly one JSON envelope and exits 0 only for `status: "complete"`. On any
+nonzero exit, unavailable/incomplete status, malformed JSON or required missing/empty section,
+stop before coding and repair the named input. Never paste a partial result as complete. A missing
+helper requires restoring this skill installation, not inventing a replacement block.
+
+For every delegated coder assignment, paste the successful envelope's literal `promptBlock` into
+the actual prompt, then append the existing advisory decision-recall block once. Keep the source
+paths below for deeper reading. For single-agent in-session coding, read this generated block
+directly before implementing. Requirements and plan are included in full; each ADR supplies its
+Decision and Confirmation with source labels. M/L/XL require at least one ADR; S can have none.
+
+The same canonical helper is used by the programmatic Workflow before code checkpoint lookup.
+It fingerprints full current inputs and binds the prompt separately, so changed documents cannot
+reuse old code. The plain mode boundary is an executable helper command plus these required
+read/embedding instructions; there is no separately automated plain dispatcher. Pure/fixture tests
+do not establish a live model relay's authenticity. Helper bounds are 64 documents, 256 KiB/file,
+1 MiB read and 96 KiB UTF-8 for the entire labelled block; exceeded bounds refuse without trimming.
+These are document limits, not a new limit on the existing coder wrapper's final prompt.
+
 Before writing any code:
 - [ ] Read existing similar implementations in codebase
 - [ ] Identify naming conventions (files, classes, functions, variables)