@dzhechkov/keysarium 1.5.29 → 1.5.31

package/README.md

@@ -29,6 +29,7 @@ After installation, open Claude Code in your project directory and start using s
 | Component | Count | Description |
 |-----------|-------|-------------|
 | **Skills** | 12 | `explore`, `frontend-design`, `goap-research-ed25519`, `presentation-storyteller`, `problem-solver-enhanced`, `reverse-engineering-unicorn`, `knowledge-extractor`, `ai-factory-mapper`, `analyst-manual-full`, `edu-site-generator`, `transcript-site-generator`, `feature-adr` |
+| | | *bundled `feature-adr` at pipeline v1.3.60: amendment-Confirmation discipline (AM-N → named falsifying test), derived `🚦 Gates` checkpoint line, opt-in Step-10 Delivery Gate (4-plane post-implementation review)* |
 | **Commands** | 20 | `/casarium`, `/new-research`, `/parallel-research`, `/discovery`, `/explore-case`, `/research`, `/cjm-prototype`, `/solve`, `/architecture-phase`, `/presentation`, `/harvest`, `/brain-export`, `/brain-import`, `/bto-benchmark`, `/feature-adr`, `/init-platform`, `/learning-stats`, `/dream`, `/workers`, `/analyst-manual` |
 | **Rules** | 14 | `research-quality`, `checkpoint-protocol`, `agent-swarm`, `domain-specific`, `anti-patterns`, `file-conventions`, `modular-reuse`, `feedback-loops`, `model-routing`, `trust-tiers`, `background-workers`, `dream-cycles`, `reward-learning`, `feature-adr-conventions` |
 | **Shards** | 9 | Context shards for each phase: `phase-0-discovery`, `phase-1-explore`, `phase-2-research`, `phase-25-cjm`, `phase-3-solve`, `phase-4-architecture`, `phase-5-presentation`, `phase-ai-factory`, `feature-adr` |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dzhechkov/keysarium",
-  "version": "1.5.29",
+  "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

@@ -53,7 +53,8 @@ Trigger on:
 │   ├── 06-implementation-plan.md      ← Step 6: SPARC-GOAP planning (enhanced)
 │   ├── 07-code.md                     ← Step 7: Code generation
 │   ├── 08-qe.md                       ← Step 8: QE + brutal-honesty review (enhanced)
-│   └── 09-fleet-qe.md                 ← Step 9: Fleet QE assessment (NEW)
+│   ├── 09-fleet-qe.md                 ← Step 9: Fleet QE assessment (NEW)
+│   └── 10-delivery-gate.md            ← Step 10: Delivery Gate (opt-in, post-implementation)
 ├── references/
 │   ├── complexity-matrix.md           ← S/M/L/XL criteria & step activation
 │   ├── adr-template.md                ← ADR document template
@@ -140,6 +141,7 @@ Step                         | S | M | L | XL | Model  | Agentic QE Skill
 7  Code                      | ✓ | ✓ | ✓ | ✓  | opus   | —                      |
 8  QE + Brutal Honesty       | ✓ | ✓ | ✓ | ✓  | sonnet | brutal-honesty-review  |
 9  Fleet QE Assessment       | - | - | ✓ | ✓  | sonnet | qe-req-val + risk-based + integration + regression + coverage |
+10 Delivery Gate (OPT-IN)    | o | o | o | o  | cross-family of coder | 4 planes: regressions ‖ security ‖ code-quality ‖ product-honesty (o = runs only when explicitly requested; absent ⇒ byte-identical) |
 ```
 
 ## DAG Dependencies
@@ -251,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
@@ -271,6 +274,7 @@ features/<feature-slug>/
 | Step 7 | `<promise>FEATURE_ADR_IMPLEMENTED</promise>` |
 | Step 8 | `<promise>FEATURE_ADR_VERIFIED</promise>` |
 | Step 9 | `<promise>FEATURE_ADR_FLEET_VERIFIED</promise>` |
+| Step 10 (opt-in) | `<promise>FEATURE_ADR_DELIVERY_GATED</promise>` |
 
 ## External Skills (loaded as needed)
 
@@ -589,7 +593,7 @@ npx @dzhechkov/skills-feature-adr init --with-learning --knowledge-extractor
 <promise>[PROMISE_TAG]</promise>
 Tier: {COMPLEXITY_TIER} | Active Steps: {ACTIVE_STEPS}
 🎓 Learning: {recalled} patterns recalled for this feature, {stored} new stored this run
-🚦 Gates: challenge-panel ✓ · claim-check ✓ · discrimination not-run · amendments ✓ · fleet —
+🚦 Gates: challenge-panel ✓ · claim-check ✓ · discrimination not-run · amendments ✓ · fleet — · delivery n/a
 
 [2-3 line summary]
 Artifacts: [list] ✅
@@ -611,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

@@ -0,0 +1,67 @@
+# Step 10: Delivery Gate (opt-in) — review the feature as a PUBLISHED ENTITY
+
+> **Opt-in.** This step runs only when explicitly requested (the user asks for a delivery gate, or the
+> workflow form receives `args.deliveryGate: true` / `args.models.delivery`). Absent ⇒ the pipeline is
+> byte-identical to a run without Step 10 — no agents, no artifact.
+
+## Why a separate step (not more Step-8)
+
+Step 8 reviews the code as the coder's counterpart — pre-hand-off, working-tree view. Step 10 reviews the
+feature as a **published entity**: the landed diff, its docs and claims, its behavior as a consumer will
+meet it. Its distinctive plane — **product honesty** — is absent from Step 8 entirely: fabricated
+completeness (output presented as complete when a source was unavailable), a feature that does less than
+its description, misleading user-facing text. Origin: a real incident where a 2-agent fresh-eyes pass said
+SHIP and only the full multi-plane review found the fabricated-completeness and cap-violation defects.
+
+## Protocol
+
+### 1. Four orthogonal planes (parallel, cross-family of the coder)
+
+Each plane reads `07_code_changes/change_manifest.md` + the actual changed files (+ `git diff` for anything
+uncommitted), calibrating on `architecture/vision.md` / `architecture/degradations.md` **when present** (an
+accepted degradation is NOT a finding) and staying generic when absent:
+
+| Plane | Hunts |
+|---|---|
+| **Regressions** | broken consumers/contracts; NEW I/O on previously-pure startup/lifespan/health paths without a negative resource-down test; removed/weakened tests (fixture-swap); silent semantic changes to shared surfaces |
+| **Security** | injection via interpolated paths/refs/commands; secrets in code/artifacts; path traversal/symlink escapes; fail-open where the contract says fail-closed |
+| **Code quality** | god-object growth; parallel implementations vs the reuse map; structurally-dead safeguards; swallowed errors |
+| **Product honesty + common sense** | claims not backed by behavior; fabricated completeness; docs/READMEs promising more than the code does; misleading degradation/limits text |
+
+Findings shape: `{severity: BLOCKER|HIGH|MED|LOW, title, where (file:line), why}` — confirmed only.
+
+### 2. Cross-validation (BLOCKER/HIGH, by index)
+
+Every BLOCKER/HIGH is independently cross-validated by a second agent, matched **positionally by index —
+never by title** (duplicate titles cross-contaminate). Default-to-FP when uncertain. A validator outage
+surfaces the findings **UNVALIDATED** — never silently dropped, never silently confirmed.
+
+### 3. Machine-checkable hand-off criterion
+
+Write `features/<slug>/10_delivery_review.md`:
+- **## 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 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 `—`.
+- **## Note** — ADVISORY: the owner decides; nothing auto-aborts.
+
+### Hard rules
+
+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 (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>` — 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).