@dzhechkov/keysarium 1.5.30 → 1.5.31

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dzhechkov/keysarium",
-  "version": "1.5.30",
+  "version": "1.5.31",
   "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/templates/.claude/skills/feature-adr/SKILL.md

@@ -253,6 +253,7 @@ features/<feature-slug>/
 │   └── change_manifest.md             ← List of modified files
 ├── 08_qe_report.md                    ← Always (brutal-honesty review)
 ├── 09_fleet_qe_assessment.md          ← L/XL only (fleet assessment)
+├── 10_delivery_review.md              ← Opt-in (Step 10 Delivery Gate verdict + findings)
 ├── diagrams/                          ← M+ only
 │   ├── architecture-c4.mermaid
 │   ├── sequence-*.mermaid
@@ -614,4 +615,5 @@ NOT running one loud: a skipped gate shows as `not-run` by construction instead
 checklist to it is the cheapest way to harden orchestrator judgment). Gate sources: challenge-panel → its
 verdict exists; claim-check → its JSON counts (`high-findings` vs `clean`); discrimination → the
 `dz discrimination-check` aggregate; amendments → every `AM-N` row carries its `→ test` and it was checked;
-fleet → the 09 artifact (L/XL only, else `—`).
+fleet → the 09 artifact (L/XL only, else `—`); delivery → the 10_delivery_review.md Verdict
+(`ready|blocked|errored`, `n/a` when the gate was not requested).

package/templates/.claude/skills/feature-adr/modules/10-delivery-gate.md

@@ -39,9 +39,9 @@ surfaces the findings **UNVALIDATED** — never silently dropped, never silently
 ### 3. Machine-checkable hand-off criterion
 
 Write `features/<slug>/10_delivery_review.md`:
-- **## Verdict** — `hand-off: ready | blocked` (ready ⇔ 0 BLOCKER and 0 unwaived HIGH, cross-validation complete)
+- **## Verdict** — `hand-off: ready | blocked | errored` (ready ⇔ 0 BLOCKER and 0 HIGH, ALL planes returned a usable result, cross-validation complete; `errored` = the gate itself failed — advisory, documented). Waivers: not in v1 — a HIGH is a HIGH.
 - **## Findings** — table: severity | plane | title | where | why | crossValidated
-- **## Hand-off criterion** — machine-checkable rows: `0 BLOCKER: PASS/FAIL(n)`, `0 unwaived HIGH: PASS/FAIL(n)`.
+- **## Hand-off criterion** — machine-checkable rows: `0 BLOCKER: PASS/FAIL(n)`, `0 HIGH: PASS/FAIL(n)` (waivers: not in v1).
   Projects with a merge-request flow add THEIR OWN rows here (`CI terminal: …`, `draft→ready: …`) — these are
   **document rows the owner fills**, never API calls made by the pipeline. No merge-request flow ⇒ the rows
   stay `—`.
@@ -52,12 +52,16 @@ Write `features/<slug>/10_delivery_review.md`:
 1. **Findings only.** Step 10 NEVER posts to a VCS host, tracker, or any external service. Publishing a
    review anywhere is a separate, explicit user instruction.
 2. **Advisory.** `hand-off: blocked` is a report, not an abort (a false gate kills trust).
-3. **Cross-family.** The planes run on the other model family than the coder (the Step-8 rule) — a model
-   must not deliver-gate its own code.
+3. **Cross-family (honest v1 scope).** The guarantee holds when the coder was Codex (Claude planes review
+   it — genuinely cross-family). A Claude-coded run gets Claude planes too — SAME family — because codex
+   planes are unsupported in v1 (a plane is a data-returning stage; the codex wrapper returns a stub, which
+   the codex-routing-honesty rule forbids). The degradation is recorded loudly: `crossFamily: false` in the
+   result and the review doc — run an independent cross-family review manually for the full guarantee.
 4. **Cost control.** One gate per hand-off, not per commit. A stack of related changes gets one Step-10 pass
    on the combined diff.
 
 ## Promise tag
 
-`<promise>FEATURE_ADR_DELIVERY_GATED</promise>` — and the `🚦 Gates:` line gains `delivery ready|blocked`
-(derived from the review doc's Verdict, `n/a` when the gate was not requested).
+`<promise>FEATURE_ADR_DELIVERY_GATED</promise>` — emitted ONLY when the gate ran AND `10_delivery_review.md`
+actually landed (the workflow probes the file; a verdict without its doc never claims the tag). The `🚦 Gates:`
+line gains `delivery ready|blocked|errored` (`n/a` when the gate was not requested).