@dzhechkov/skills-feature-adr 1.3.5 → 1.3.6

package/README.md

@@ -373,6 +373,45 @@ npx @dzhechkov/skills-feature-adr init --with-learning --knowledge-extractor
 
 ---
 
+## Self-Learning Layers
+
+There are **three independent self-learning systems** that can sit under a Feature ADR run.
+`--full-qe-extended` does **not** turn on learning by itself — it controls QE depth. Learning is a
+separate, orthogonal concern. The three layers do **not conflict**: each is isolated by its own
+storage path, its own learning signal, and its own consumer.
+
+| Layer | Turn it on with | Learns from | Storage (distinct!) | Needs a DB? |
+|-------|-----------------|-------------|---------------------|-------------|
+| **A — feature-adr reward learning** | install flag **`--with-learning`** (or bundled with `@dzhechkov/keysarium`) | your **checkpoint responses** (`ок`=1.0 / minor=0.7 / rework=0.3 / restart=0.0) | `.keysarium/memory/*.json` | **No** — plain JSON files |
+| **B — agentic-qe learning** | comes with `agentic-qe` (required by `--full-qe` / `--full-qe-extended`), initialized by `aqe init` | QE task **experiences** (ReasoningBank + dream scheduler) | `.agentic-qe/memory.db` + `patterns.rvf` | Self-contained (its own store) |
+| **C — dz harness self-learning** | the `dz` CLI (`dz setup` / `dz teach` / `dz consolidate` / `dz recall`) | your **dz sessions** | `.dz/` (+ optional `.dz/agentdb.db` vector tier) | **Optional** — lexical works without one; agentdb only adds vector search |
+
+### Do they conflict? No — but observe one rule
+
+- **No logical conflict:** different files, different signals, different readers → no write
+  contention and no data clobbering. Enabling all three at once is fine; they're complementary.
+- **Auto-dedup:** if `@dzhechkov/keysarium` is present, the installer **skips** `--with-learning`
+  (keysarium already ships layer A), so you can't accidentally double-install it.
+- **⚠️ The one rule — one DB file per writer.** Layer C writes to SQLite **natively (better-sqlite3,
+  WAL)**; agentic-qe (layer B) can write **via sql.js (whole-file overwrite)**. Pointing *both* at
+  the **same** `.db` file risks corruption. By default they use **different files**
+  (`.agentic-qe/memory.db` ≠ `.dz/agentdb.db`), so out of the box you're safe — just never
+  hand-repoint one system's `AGENTDB_PATH` at the other's database.
+
+### Which to enable
+
+- Writing features with this pipeline and want it to **learn from your feedback** →
+  `npx @dzhechkov/skills-feature-adr init --with-learning` (**no agentdb needed**).
+- Running `--full-qe` / `--full-qe-extended` → agentic-qe's learning already runs via its hooks.
+- Living inside the `dz` harness and want cross-session memory → `dz setup` (add agentdb only if you
+  want the vector tier).
+
+> There is no single unified "what did the whole stack learn" view — each layer reports from its own
+> store. That's the price of isolation (and the reason there are no cascading failures). Tune each
+> where it lives.
+
+---
+
 ## Shared Skills
 
 Feature ADR uses these skills from `@dzhechkov/keysarium` (if installed):

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dzhechkov/skills-feature-adr",
-  "version": "1.3.5",
+  "version": "1.3.6",
   "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.",
   "main": "src/cli.js",
   "bin": {