@dzhechkov/keysarium 1.5.7 → 1.5.11

package/package.json

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

@@ -216,7 +216,7 @@ After Step 8 (or Step 9 for L/XL) completes, verify:
 | `{COMPLEXITY_TIER}` | Step 0 | All steps | S/M/L/XL |
 | `{ACTIVE_STEPS}` | Step 0 | Orchestrator | list[int] |
 | `{TIME_BUDGET}` | Step 0 | All steps | dict |
-| `{LEARNED_PATTERNS}` | Step 0 | Step 1 (brief); Steps 8-9 do their own namespace recalls | list[pattern] (Direct modes only) |
+| `{LEARNED_PATTERNS}` | Step 0 | Step 1 (brief); Steps 8-9 do their own namespace recalls | list[pattern] (dz recall = ALL modes; aqe adds semantic in Direct modes) |
 | `{REQUIREMENTS}` | Step 1 | Steps 2-9 | structured |
 | `{RESEARCH_FINDINGS}` | Step 2 | Steps 3-5 | structured |
 | `{ADR_DECISIONS}` | Step 3 | Steps 3.5-7 | list[ADR] |
@@ -343,9 +343,31 @@ Step 0 (Complexity Router) checks:
 3. If flag + installed → set `{AGENTIC_QE_MODE}` = `direct` or `direct-extended`
 4. If flag present but not installed → WARN and fall back to reference mode
 
-### Pattern memory loop (Direct modes)
+### Ultracode → the deterministic workflow form
 
-When `{AGENTIC_QE_MODE}` = `direct` | `direct-extended`, the pipeline runs a recall → store cycle
+`/feature-adr` runs in TWO forms, same pipeline:
+- **Plain `/feature-adr`** (no ultracode) — *agent-driven*: an agent follows these SKILL instructions
+  step by step.
+- **ultracode + `--full-qe-extended`** — *harness-driven*: the harness runs the bundled deterministic
+  workflow `.claude/workflows/feature-adr.js` (shipped with this pack), which fans the steps out across
+  subagents, produces the `features/<slug>/00-09` artifacts, and runs the agentic-qe QE + self-learning
+  inline. Invoke it via `Workflow({ scriptPath: '.claude/workflows/feature-adr.js', args: { slug,
+  description, code, tier, stopAfter, repo, dzBin } })`. Hybrid checkpoints: S/M autonomous; L/XL return
+  after the Plan phase for your steer. See `.claude/rules/feature-adr-ultracode.md`.
+
+### Pattern memory loop (self-learning — runs in ALL modes)
+
+**Self-learning is MANDATORY on EVERY `/feature-adr` run — including plain `/feature-adr` without any
+`--full-qe` flag and outside ultracode.** The **dz durable loop runs UNCONDITIONALLY** (no MCP, no
+`fleet_init` needed): **Step 0** `dz recall "<domain terms>"` → fold the top patterns into
+`{LEARNED_PATTERNS}` → apply in Step 1; **Step 8** `dz teach "<durable lesson>"` for each real lesson;
+each step records the live panel via `dz statusline --fa-record`. This half NEVER depends on the mode.
+
+The **agentic-qe MCP layer below is an ADDITIONAL enrichment, active only in Direct modes**
+(`--full-qe` / `--full-qe-extended`, needs `fleet_init`) — it adds semantic in-session recall on top of
+the always-on dz loop.
+
+When `{AGENTIC_QE_MODE}` = `direct` | `direct-extended`, the pipeline ALSO runs a recall → store cycle
 over agentic-qe's MCP pattern memory (`namespace: "learning"`, `fleet_init` first):
 
 - **Step 0** — `memory_query("patterns/feature-adr/*")` **plus** `dz recall --json` over the durable
@@ -364,7 +386,7 @@ observed live), so it serves fast in-session semantic recall; the dz lexical sto
 (`dz teach`/`dz recall`) is the durable half that survives to the next day. All calls are
 non-blocking — an error or empty result never stalls the pipeline. This layer is
 **distinct from the Keysarium reward layer** installed by `--with-learning`: it uses agentic-qe MCP
-memory + the dz store, is gated on Direct modes only, and never touches `.keysarium/memory/`.
+memory + the dz store, is UNCONDITIONAL for the dz half (recall/teach/fa-record run in every mode) and Direct-mode-only for the aqe-MCP half, and never touches `.keysarium/memory/`.
 
 **Live learning panel (`dz statusline`).** The pipeline **drives** the panel: at each pattern-memory-loop
 step above it records its live state via `dz statusline --fa-record …`, so `dz statusline` can surface