@dzhechkov/p-replicator 1.10.3 → 1.12.0

package/README/ru/02_user_guide.md

@@ -502,7 +502,7 @@ npx @dzhechkov/p-replicator verify
 ```
 
 Должен показать:
-- ✅ Pre-shipped contract intact (10 skills + 11 commands + 4 agents + 6 rules + settings.json)
+- ✅ Pre-shipped contract intact (10 skills + 11 commands + 4 agents + 9 rules + settings.json)
 - ✅ Post-/replicate hints — для Mode 2 многие будут отсутствовать (это нормально)
 - 📊 Per-feature artifacts: `docs/features/<id>/01_specification.md`...`05_completion.md`,
   `validation-report.md`, `review-report.md`

package/README/ru/03_admin_guide.md

@@ -83,7 +83,7 @@ P-Replicator V1.5.0 ● user │ Sonnet 4.7
 🚀 Pipeline   /<cmd> ▓▓▓░░░░ 50%  │ Phase: VALIDATE (2/4)  │ Last: /replicate
 🎯 Roadmap    [●●●○○○○○] mvp 3/8   │ Done 5/12  │ ▶ auth-jwt  │ Domain: banking
 📊 SPARC      ●11/11  │ 🟢 78/100  │ Plans ●3  │ ADRs ●2  │ Harvest 2026-05-05
-🛠️ Toolkit   Skills ●10/10 │ Cmds ●11/11 │ Agents ●4+3 │ Rules ●6+2 │ Hooks ●7/7
+🛠️ Toolkit   Skills ●10/10 │ Cmds ●11/11 │ Agents ●4+3 │ Rules ●9+2 │ Hooks ●7/7
 💡 Insights   ●12 (2026-05-06) │ Tests 85/85 ✓ │ MCP ●1/1 │ Settings ✓ │ 🧬 Keysarium ✓
 ```
 
@@ -248,7 +248,7 @@ echo ".claude/.last-test.json" >> .gitignore
 
 | Инструмент | Что проверяет | Когда |
 |---|---|---|
-| `npx @dzhechkov/p-replicator doctor` | Pre-shipped contract: 10 skills + 11 commands + 4 agents + 6 rules + settings.json + 7 hooks + git on PATH | После init / при подозрении что что-то сломалось |
+| `npx @dzhechkov/p-replicator doctor` | Pre-shipped contract: 10 skills + 11 commands + 4 agents + 9 rules + settings.json + 7 hooks + git on PATH | После init / при подозрении что что-то сломалось |
 | `npx @dzhechkov/p-replicator verify` | Pre-shipped + post-/replicate hints (CLAUDE.md, planner.md, security.md, feature-roadmap.json, и т.д.) | После каждого `/replicate` для уверенности |
 
 **`doctor` exit codes:**

package/README/ru/04_api_reference.md

@@ -51,7 +51,7 @@
   ],
   "shippedDefaults": {
     "settings.json": {
-      "hooks": { "SessionStart": [...], "Stop": [...] },
+      "hooks": { "SessionStart": [...], "UserPromptSubmit": [...], "Stop": [...] },
       "statusLine": { "type": "command", "command": "..." }
     }
   }
@@ -180,6 +180,7 @@ node .claude/hooks/state-update.cjs --json '{"currentCommand":"/run", ...}'
   },
   "hooks": {
     "SessionStart": [ /* matchers + hooks */ ],
+    "UserPromptSubmit": [ /* matchers + hooks */ ],
     "Stop": [ /* matchers + hooks */ ],
     "PreToolUse": [ /* user-added */ ],
     "PostToolUse": [ /* user-added */ ]
@@ -220,6 +221,7 @@ node .claude/hooks/state-update.cjs --json '{"currentCommand":"/run", ...}'
 
 **Event types в Claude Code:**
 - `SessionStart` — при начале сессии (stdout инжектится в context)
+- `UserPromptSubmit` — после появления реального пользовательского prompt (structured context)
 - `Stop` — при завершении turn'а (side-effects: commit, log)
 - `PreToolUse`, `PostToolUse` — вокруг tool-вызовов
 
@@ -299,10 +301,14 @@ const COMPONENTS = {
 
 ### `session-insights.cjs`
 
-**Trigger:** `SessionStart` hook.
-**Reads:** `.claude/insights/index.md` (`## YYYY-MM-DD` headings)
-**Writes:** stdout (Claude Code инжектит в session context)
-**Output:** до 3 свежих insights в `## Recent project insights\n\n## ... ## ... ## ...` format
+**Trigger:** hooks `SessionStart` и `UserPromptSubmit`.
+**Reads:** Markdown-источник истины `.claude/insights/index.md`; prompt-time выдача также вызывает
+optional `dz recall` с закреплённым корнем проекта.
+**Writes:** missing-carrier hint на SessionStart либо один context-envelope UserPromptSubmit.
+**Output:** только успешный непустой вывод recall подавляет локальную выдачу. Отсутствующий,
+падающий или пустой recall использует локальный fallback до 3 свежих Markdown-записей; failure
+назван, отсутствие и пустой вывод тихие. Writer сначала сохраняет Markdown и только затем делает
+best-effort идемпотентный дубль через `dz teach`, поэтому отказ проекции не стирает запись.
 
 ### `autocommit-roadmap.cjs` / `autocommit-insights.cjs` / `autocommit-plans.cjs`
 

package/README/ru/README.md

@@ -6,7 +6,7 @@ toolkit для AI-assisted разработки в Claude Code (Vibe Coding).
 ## Что это
 
 `p-replicator` устанавливает в проект готовый набор `.claude/`-инструментов:
-**11 slash-команд**, **10 skills**, **4 агента**, **6 правил**, **7 hook-скриптов**
+**11 slash-команд**, **10 skills**, **4 агента**, **9 правил**, **7 hook-скриптов**
 и `settings.json` с pre-configured хуками. Главная команда `/replicate`
 проводит проект через 5-фазный pipeline (Discovery → Planning → Validation →
 Toolkit Generation → Finalize), генерирует SPARC-документацию и project-specific

package/README/ru/html/index.html

@@ -112,7 +112,7 @@
 <h1 id="dokumentatsiya-dzhechkovp-replicator">Документация @dzhechkov/p-replicator</h1>
 <p>Полный комплект документации к npm-пакету <code>@dzhechkov/p-replicator</code> — toolkit для AI-assisted разработки в Claude Code (Vibe Coding).</p>
 <h2 id="index-chto-eto">Что это</h2>
-<p><code>p-replicator</code> устанавливает в проект готовый набор <code>.claude/</code>-инструментов: <strong>11 slash-команд</strong>, <strong>10 skills</strong>, <strong>4 агента</strong>, <strong>6 правил</strong>, <strong>7 hook-скриптов</strong> и <code>settings.json</code> с pre-configured хуками. Главная команда <code>/replicate</code> проводит проект через 5-фазный pipeline (Discovery → Planning → Validation → Toolkit Generation → Finalize), генерирует SPARC-документацию и project-specific артефакты.</p>
+<p><code>p-replicator</code> устанавливает в проект готовый набор <code>.claude/</code>-инструментов: <strong>11 slash-команд</strong>, <strong>10 skills</strong>, <strong>4 агента</strong>, <strong>9 правил</strong>, <strong>7 hook-скриптов</strong> и <code>settings.json</code> с pre-configured хуками. Главная команда <code>/replicate</code> проводит проект через 5-фазный pipeline (Discovery → Planning → Validation → Toolkit Generation → Finalize), генерирует SPARC-документацию и project-specific артефакты.</p>
 <h2 id="index-navigatsiya">Навигация</h2>
 <div class="table-wrap"><table><thead><tr><th>Раздел</th><th>Описание</th></tr></thead><tbody><tr><td><a href="#quickstart">01_quickstart.md</a></td><td>Установка, первый запуск, проверка</td></tr><tr><td><a href="#user-guide">02_user_guide.md</a></td><td>Все команды и workflow с примерами</td></tr><tr><td><a href="#admin-guide">03_admin_guide.md</a></td><td>Настройка hooks, settings.json, statusline, insights</td></tr><tr><td><a href="#api-reference">04_api_reference.md</a></td><td>CLI-флаги, схемы манифеста, roadmap, state</td></tr><tr><td><a href="#architecture">05_architecture.md</a></td><td>Архитектура: pre-shipped vs generated, SSOT, hooks</td></tr><tr><td><a href="#troubleshooting">06_troubleshooting.md</a></td><td>Решение типичных проблем</td></tr><tr><td><a href="#changelog">07_changelog.md</a></td><td>История версий 1.3.x → 1.5.x</td></tr></tbody></table></div>
 <h2 id="index-yazyki">Языки</h2>
@@ -140,7 +140,7 @@ claude                              # открыть Claude Code
 <p>В корне вашего проекта:</p>
 <pre data-lang="bash"><code class="language-bash">npx @dzhechkov/p-replicator init</code></pre>
 <p>Это создаст:</p>
-<ul><li><code>.claude/skills/</code> — 10 предустановленных skills</li><li><code>.claude/commands/</code> — 11 slash-команд (<code>/replicate</code>, <code>/run</code>, <code>/feature</code>, ...)</li><li><code>.claude/agents/</code> — 4 пайплайн-агента</li><li><code>.claude/rules/</code> — 5 governance-правил</li><li><code>.claude/hooks/</code> — 6 cross-platform Node-скриптов</li><li><code>.claude/settings.json</code> — конфигурация hooks + statusline</li><li><code>.p-replicator.json</code> — манифест установки</li></ul>
+<ul><li><code>.claude/skills/</code> — 10 предустановленных skills</li><li><code>.claude/commands/</code> — 11 slash-команд (<code>/replicate</code>, <code>/run</code>, <code>/feature</code>, ...)</li><li><code>.claude/agents/</code> — 4 пайплайн-агента</li><li><code>.claude/rules/</code> — 9 governance-правил</li><li><code>.claude/hooks/</code> — 6 cross-platform Node-скриптов</li><li><code>.claude/settings.json</code> — конфигурация hooks + statusline</li><li><code>.p-replicator.json</code> — манифест установки</li></ul>
 <p>Установка идемпотентна: <code>init</code> не перезапишет существующие файлы без флага <code>--force</code>.</p>
 <h2 id="quickstart-pervyy-zapusk">Первый запуск</h2>
 <pre data-lang="bash"><code class="language-bash">claude                                    # открыть Claude Code в проекте</code></pre>
@@ -186,7 +186,7 @@ mv docs/your-arch.md  docs/Architecture.md
 <p>После <code>/replicate</code> выполните:</p>
 <pre data-lang="bash"><code class="language-bash">npx @dzhechkov/p-replicator verify</code></pre>
 <p>Команда проверит:</p>
-<ul><li><strong>Pre-shipped contract</strong> (must-have): 10 skills + 11 commands + 4 agents + 6 rules + settings.json</li><li><strong>Post-/replicate hints</strong> (advisory): CLAUDE.md, project-specific агенты, feature-roadmap.json, security-правила и т.д.</li></ul>
+<ul><li><strong>Pre-shipped contract</strong> (must-have): 10 skills + 11 commands + 4 agents + 9 rules + settings.json</li><li><strong>Post-/replicate hints</strong> (advisory): CLAUDE.md, project-specific агенты, feature-roadmap.json, security-правила и т.д.</li></ul>
 <p>Exit code <code>0</code> означает что pre-shipped контракт цел; warnings показывают что из project-specific артефактов ещё не создано.</p>
 <p>Альтернатива (для общей health-проверки):</p>
 <pre data-lang="bash"><code class="language-bash">npx @dzhechkov/p-replicator doctor</code></pre>
@@ -213,7 +213,7 @@ mv docs/your-arch.md  docs/Architecture.md
 │   ├── skills/              # 10 skills
 │   ├── commands/            # 11 slash-команд
 │   ├── agents/              # 4 pipeline-агента
-│   ├── rules/               # 6 правил
+│   ├── rules/               # 9 правил
 │   ├── hooks/               # 6 Node-скриптов
 │   └── settings.json        # hooks + statusline config
 ├── .p-replicator.json       # манифест установки
@@ -429,7 +429,7 @@ claude
 <p>После <code>/feature</code> (или <code>/run</code>) запустите:</p>
 <pre data-lang="bash"><code class="language-bash">npx @dzhechkov/p-replicator verify</code></pre>
 <p>Должен показать:</p>
-<ul><li>✅ Pre-shipped contract intact (10 skills + 11 commands + 4 agents + 6 rules + settings.json)</li><li>✅ Post-/replicate hints — для Mode 2 многие будут отсутствовать (это нормально)</li><li>📊 Per-feature artifacts: <code>docs/features/&lt;id&gt;/01_specification.md</code>...<code>05_completion.md</code>, <code>validation-report.md</code>, <code>review-report.md</code></li></ul>
+<ul><li>✅ Pre-shipped contract intact (10 skills + 11 commands + 4 agents + 9 rules + settings.json)</li><li>✅ Post-/replicate hints — для Mode 2 многие будут отсутствовать (это нормально)</li><li>📊 Per-feature artifacts: <code>docs/features/&lt;id&gt;/01_specification.md</code>...<code>05_completion.md</code>, <code>validation-report.md</code>, <code>review-report.md</code></li></ul>
 <h4 id="user-guide-future-enhancement-m3-v-knownlimitations">Future enhancement (M3 в KNOWN_LIMITATIONS)</h4>
 <p><code>docPaths</code> config в <code>.p-replicator.json</code> для нестандартных путей доков — в roadmap'е. Tier S effort, чисто config + spec-read изменения, без изменений CLI-кода.</p>
 <hr>
@@ -551,7 +551,7 @@ Set DATABASE_URL_SHADOW env var explicitly to a separate database.
 🚀 Pipeline   /&lt;cmd&gt; ▓▓▓░░░░ 50%  │ Phase: VALIDATE (2/4)  │ Last: /replicate
 🎯 Roadmap    [●●●○○○○○] mvp 3/8   │ Done 5/12  │ ▶ auth-jwt  │ Domain: banking
 📊 SPARC      ●11/11  │ 🟢 78/100  │ Plans ●3  │ ADRs ●2  │ Harvest 2026-05-05
-🛠️ Toolkit   Skills ●10/10 │ Cmds ●11/11 │ Agents ●4+3 │ Rules ●6+2 │ Hooks ●7/7
+🛠️ Toolkit   Skills ●10/10 │ Cmds ●11/11 │ Agents ●4+3 │ Rules ●9+2 │ Hooks ●7/7
 💡 Insights   ●12 (2026-05-06) │ Tests 85/85 ✓ │ MCP ●1/1 │ Settings ✓ │ 🧬 Keysarium ✓</code></pre>
 <p><strong>Источники (heuristic + state-file):</strong></p>
 <div class="table-wrap"><table><thead><tr><th>Метрика</th><th>Откуда</th></tr></thead><tbody><tr><td>Pipeline command + phase + progress</td><td><code>.claude/.p-replicator-state.json</code> (state-file)</td></tr><tr><td>Roadmap progress</td><td><code>.claude/feature-roadmap.json</code></td></tr><tr><td>SPARC count</td><td><code>docs/{PRD,Architecture,...}.md</code> files</td></tr><tr><td>Validation score</td><td>regex extract from <code>docs/validation-report.md</code></td></tr><tr><td>Plans count</td><td><code>docs/plans/*.md</code></td></tr><tr><td>ADRs count</td><td><code>docs/ADR.md</code> <code>## ADR-...</code> headings, или <code>docs/adr/*.md</code>, или <code>docs/ddd/adr/*.md</code></td></tr><tr><td>Insights count + last date</td><td><code>## YYYY-MM-DD</code> headings в <code>.claude/insights/index.md</code></td></tr><tr><td>Toolkit counts</td><td>filesystem walk <code>.claude/{skills,commands,agents,rules,hooks}/</code></td></tr><tr><td>Settings status</td><td>deep-equals current vs <code>manifest.shippedDefaults</code> → <code>defaults</code>/<code>merged</code></td></tr><tr><td>MCP servers</td><td><code>.mcp.json</code></td></tr><tr><td>Domain</td><td>keyword grep <code>CLAUDE.md</code> (banking/retail/enterprise/healthcare)</td></tr><tr><td>Last harvest</td><td><code>TOOLKIT_HARVEST.md</code> mtime</td></tr><tr><td>Last test</td><td>optional <code>.claude/.last-test.json</code> cache</td></tr></tbody></table></div>
@@ -638,7 +638,7 @@ echo ".claude/.last-test.json" &gt;&gt; .gitignore</code></pre>
 <p><strong>Auto-commit</strong> через <code>autocommit-roadmap.cjs</code> (Stop hook) при изменениях.</p>
 <hr>
 <h2 id="admin-guide-doctor-verify-dva-raznyh-instrumenta">Doctor + Verify — два разных инструмента</h2>
-<div class="table-wrap"><table><thead><tr><th>Инструмент</th><th>Что проверяет</th><th>Когда</th></tr></thead><tbody><tr><td><code>npx @dzhechkov/p-replicator doctor</code></td><td>Pre-shipped contract: 10 skills + 11 commands + 4 agents + 6 rules + settings.json + 7 hooks + git on PATH</td><td>После init / при подозрении что что-то сломалось</td></tr><tr><td><code>npx @dzhechkov/p-replicator verify</code></td><td>Pre-shipped + post-/replicate hints (CLAUDE.md, planner.md, security.md, feature-roadmap.json, и т.д.)</td><td>После каждого <code>/replicate</code> для уверенности</td></tr></tbody></table></div>
+<div class="table-wrap"><table><thead><tr><th>Инструмент</th><th>Что проверяет</th><th>Когда</th></tr></thead><tbody><tr><td><code>npx @dzhechkov/p-replicator doctor</code></td><td>Pre-shipped contract: 10 skills + 11 commands + 4 agents + 9 rules + settings.json + 7 hooks + git on PATH</td><td>После init / при подозрении что что-то сломалось</td></tr><tr><td><code>npx @dzhechkov/p-replicator verify</code></td><td>Pre-shipped + post-/replicate hints (CLAUDE.md, planner.md, security.md, feature-roadmap.json, и т.д.)</td><td>После каждого <code>/replicate</code> для уверенности</td></tr></tbody></table></div>
 <p><strong><code>doctor</code> exit codes:</strong></p>
 <ul><li><code>0</code> — всё в порядке</li><li><code>1</code> — что-то отсутствует из must-have (используйте <code>init --force</code> для repair)</li></ul>
 <p><strong><code>verify</code> exit codes:</strong></p>

package/README.md

@@ -11,10 +11,10 @@
 [![License](https://img.shields.io/badge/License-MIT-22c55e.svg?style=for-the-badge)](https://opensource.org/licenses/MIT)
 [![Node](https://img.shields.io/badge/node-%E2%89%A516-339933?style=for-the-badge&logo=node.js&logoColor=white)](https://nodejs.org)
 
-[![Tests](https://img.shields.io/badge/tests-105%2F105-22c55e?style=flat-square)](#test-infrastructure)
+[![Tests](https://img.shields.io/badge/tests-440%20pass%20%7C%203%20skip-22c55e?style=flat-square)](#test-infrastructure)
 [![Skills](https://img.shields.io/badge/skills-10-8b5cf6?style=flat-square)](#skills-reference)
 [![Commands](https://img.shields.io/badge/slash%20commands-11-f59e0b?style=flat-square)](#commands-reference)
-[![Hooks](https://img.shields.io/badge/hooks-6-3b82f6?style=flat-square)](#hooks-system)
+[![Hooks](https://img.shields.io/badge/hooks-10-3b82f6?style=flat-square)](#hooks-system)
 [![SPARC Pipeline](https://img.shields.io/badge/SPARC-5%20phases-ec4899?style=flat-square)](#pipeline-overview--replicate-phases)
 
 <br>
@@ -101,7 +101,7 @@
 
 ## 📖 What is p-replicator?
 
-`@dzhechkov/p-replicator` installs a ready-made `.claude/` toolkit into any project: **11 slash commands**, **10 skills**, **4 agents**, **6 rules**, **9 hook scripts**, and a `settings.json` with pre-configured hooks and a multi-line statusline dashboard.
+`@dzhechkov/p-replicator` installs a ready-made `.claude/` toolkit into any project: **11 slash commands**, **10 skills**, **4 agents**, **9 rules**, **10 hook utilities**, and a `settings.json` with pre-configured hooks and a multi-line statusline dashboard.
 
 The flagship `/replicate` command takes a project through a **5-phase pipeline**:
 
@@ -262,8 +262,8 @@ This creates:
 - `.claude/skills/` — 10 pre-shipped skills
 - `.claude/commands/` — 11 slash commands (`/replicate`, `/run`, `/feature`, ...)
 - `.claude/agents/` — 4 pipeline agents
-- `.claude/rules/` — 5 governance rules
-- `.claude/hooks/` — 6 cross-platform Node scripts
+- `.claude/rules/` — 9 governance rules
+- `.claude/hooks/` — 10 cross-platform Node scripts
 - `.claude/settings.json` — hooks + statusline configuration
 - `.p-replicator.json` — install manifest
 
@@ -289,9 +289,9 @@ This creates:
 | **Skills** | 10 | 92 files (880K+ chars — MEASURED via `wc -c` over `templates/.claude/skills`: 880,679). Modular architecture: foundation → composite → master orchestrator |
 | **Commands** | 11 | `/replicate`, `/harvest`, `/start`, `/plan`, `/feature`, `/go`, `/run`, `/next`, `/myinsights`, `/docs`, `/deploy` |
 | **Agents** | 4 | `replicate-coordinator`, `product-discoverer`, `doc-validator`, `harvest-coordinator` |
-| **Rules** | 6 | `replicate-pipeline`, `skill-interface-protocol`, `git-workflow`, `insights-capture`, `feature-lifecycle`, `docker-ports` |
-| **Hooks** | 9 | `session-insights`, `autocommit-{roadmap,insights,plans}`, `statusline`, `state-update`, `check-ports`, `check-growth-trace`, `check-docs-complete` (cross-platform Node) |
-| **Settings** | 1 | `settings.json` with statusLine + SessionStart + Stop hooks pre-configured |
+| **Rules** | 9 | `cost-of-detection-ladder`, `replicate-pipeline`, `skill-interface-protocol`, `git-workflow`, `insights-capture`, `feature-lifecycle`, `docker-ports`, `swarm-file-evidence`, `honest-configuration` |
+| **Hooks** | 10 | Ten cross-platform Node utilities, including the harvest insight writer |
+| **Settings** | 1 | `settings.json` with statusLine + SessionStart + UserPromptSubmit + Stop hooks pre-configured |
 
 After running `/replicate`, the toolkit also generates **project-specific** artifacts:
 
@@ -326,13 +326,15 @@ Discovery Brief was never written to disk at all. Since 1.7.0:
 
 What none of this proves: that anything was built, or that copying a competitor's move is lawful.
 
-## 🔎 The three deliberate checks
+## 🔎 Deliberate checks
 
-Six of the nine hook scripts run themselves. Three do not: they are utilities you invoke when you want
+Six of the nine hook utilities run themselves. Three do not: they are utilities you invoke when you want
 an answer, and they are wired to no event on purpose. A hook of this package is **non-blocking by
 contract** — it can print, never refuse — so a check that must be able to say "no" cannot be one.
+The package also ships the non-hook Bash traceability checker described after those three utilities;
+`/feature` invokes it as a blocking pipeline gate.
 
-Both answer with **three** exit codes, and the third is the one that matters:
+Each answers with **three** exit codes, and the third is the one that matters:
 
 | Code | Meaning |
 |:---:|---|
@@ -346,7 +348,8 @@ why a missing config, a missing docker, or a missing brief is `2` and never `0`.
 ### `check-ports.cjs` — no database faces the internet
 
 ```bash
-node .claude/hooks/check-ports.cjs .
+node .claude/hooks/check-ports.cjs .          # catalog: one Compose project
+node .claude/hooks/check-ports.cjs --machine  # point-in-time snapshot of the current Docker context
 ```
 
 ```
@@ -355,9 +358,25 @@ node .claude/hooks/check-ports.cjs .
      Убрать ports: целиком, либо привязать к 127.0.0.1
 ```
 
-Reads the normalised config (`docker compose config`), so the short port form and `extends` are
-already resolved. Catches `network_mode: host` and services published beside a reverse-proxy too.
-A loopback bind (`127.0.0.1:` or `[::1]:`) is legal and passes — that exception is part of the rule.
+Catalog mode reads one normalised config (`docker compose config`), so the short port form and
+`extends` are already resolved. It catches `network_mode: host` and services published beside a
+reverse-proxy, but it never queries running containers. Its clean receipt is limited to that selected
+catalog. A loopback bind (`127.0.0.1:` or `[::1]:`) is legal in catalog mode — that exception remains
+part of the rule.
+
+For Redis/Memcached, catalog mode also classifies visible authentication configuration: established
+absence of a password is `1`, while a config-bearing volume/custom image that can hide the answer is
+`2`, never a guessed clean result. The catalog loopback exception is applied first and remains legal.
+
+Machine mode enumerates recognised running storage containers in the current Docker context, inspects
+their live bind addresses and Compose ownership labels, and probes live Redis authentication there
+only. Its clean receipt is a point-in-time snapshot, not continuous monitoring and not a claim about
+stopped containers or another Docker context. A live loopback Redis without a password is reported as
+a separate violation even though the catalog loopback exception remains legal.
+
+Both scopes preserve the same contract: `0` means the selected scope was checked clean, `1` means a
+violation was established, and `2` means **the check did not run to completion** (`проверка НЕ
+ВЫПОЛНЕНА`) because Docker/config/permissions or a required runtime observation was unavailable.
 
 **When to run it:** after writing or editing `docker-compose.yml`, and before any deploy.
 
@@ -408,6 +427,48 @@ A conscious rejection **with a reason written down** passes; a silent drop does
 **What it does NOT prove:** that anything was built, or that copying a competitor's growth move is
 lawful. It proves an obligation was carried forward, nothing more.
 
+### `check-pipeline-gaps.sh` — FR/NFR/AC keys are joins, not decoration
+
+The package owns the checker at `scripts/check-pipeline-gaps.sh`. `/feature` resolves that packaged
+file directly, so an installed consumer runs the same executable without copying it onto the hooks
+surface:
+
+```bash
+CHECK_PIPELINE_GAPS="$(node -p "require.resolve('@dzhechkov/p-replicator/scripts/check-pipeline-gaps.sh')")" || {
+  printf 'NOT-ESTABLISHED packaged checker could not be resolved\n' >&2
+  exit 2
+}
+bash "$CHECK_PIPELINE_GAPS" "${CLAUDE_PROJECT_DIR:-.}" --traceability
+```
+
+The checker reads complete `DOCUMENT_ROLE_MAP` blocks from the installed `/feature` command and
+`sparc-prd-mini` skill. It checks the applicable project-level pair and every immediate
+`docs/features/*/` contour independently. It never rediscovers `01_specification.md` or
+`02_pseudocode.md` by basename.
+
+Accepted specification declarations are level-three headings such as
+`### FR-order-refund-1`, `### NFR-order-refund-2 — latency`, and
+`### AC-order-refund-3 - accepted`. Pseudocode evidence is a standalone
+``REQUIREMENT: `FR-order-refund-1` `` line inside an `### Algorithm:` block. Prose, comments,
+tables, and nested `SC-FR-*` identifiers are ignored. Duplicate or malformed declarations block.
+
+For each contour it runs both sorted differences: specification→pseudocode names requirements with
+no algorithm claim; pseudocode→specification names dangling claims. Every gap is printed with its
+contour, direction, and exact key. Exit `0` means every readable contour was checked and both sets
+match; exit `1` means a named content/traceability gap; exit `2` means the map or filesystem evidence
+was not trustworthy enough to compare. `/feature` preserves both non-zero states before Phase 2.
+
+Symlinked contours or role files are refused rather than followed outside the declared root. Matching
+keys prove cross-document linkage only; they do not prove that an algorithm semantically implements
+the requirement.
+
+**Scope and provenance.** This package executable implements the ADR-owned traceability decision
+only: role-map resolution, project plus immediate-feature traversal, structural FR/NFR/AC
+declarations, both `comm -23` directions, duplicate/malformed/symlink refusal, exact diagnostics,
+and blocking `0/1/2` exits. It deliberately does not carry the old workspace-only PR-001/PR-002/
+PR-004/PR-007, weekly-metric, port, or `[GAP]` umbrella checks. The workspace source is not needed
+by an installed consumer.
+
 ## ✅ Verify the install
 
 After `/replicate`, run:
@@ -418,7 +479,7 @@ npx @dzhechkov/p-replicator verify
 
 The command checks:
 
-- **Pre-shipped contract** (must-have): 10 skills + 11 commands + 4 agents + 6 rules + settings.json + 9 hooks
+- **Pre-shipped contract** (must-have): 10 skills + 11 commands + 4 agents + 9 rules + settings.json + 10 hooks
 - **Post-/replicate hints** (advisory): CLAUDE.md, project-specific agents, feature-roadmap.json, security rules, etc.
 
 **Exit codes:**
@@ -431,7 +492,9 @@ The command checks:
 npx @dzhechkov/p-replicator doctor
 ```
 
-`doctor` verifies pre-shipped contract + Prerequisites (`git on PATH`). Stricter than `verify` for must-have components.
+`doctor` verifies pre-shipped contract + Prerequisites (`git on PATH`). It also prints the
+informational, non-gating insight-flow observation described below. It remains stricter than
+`verify` for must-have components.
 
 ---
 
@@ -615,7 +678,8 @@ while features in scope:
 
 ### `/myinsights` — knowledge capture
 
-Build a project-local knowledge base of "rakes" (development insights) that auto-inject into every session via the SessionStart hook.
+Build a project-local knowledge base of "rakes" (development insights). Markdown remains the source
+of truth; `UserPromptSubmit` uses optional dz recall with a local fallback.
 
 ```bash
 /myinsights                                                  # interactive prompt
@@ -623,12 +687,23 @@ Build a project-local knowledge base of "rakes" (development insights) that auto
 /myinsights recall prisma                                    # search by keyword
 ```
 
-Storage: `.claude/insights/index.md` — markdown log auto-committed by Stop hook.
+Storage: `.claude/insights/index.md` — Markdown log auto-committed by Stop hook. A successful,
+non-empty dz recall result may own prompt-time delivery; absent, failing, or empty recall uses the
+local last-three fallback.
 
 ### `/harvest` — knowledge extraction
 
 Extract reusable patterns from a completed project into a knowledge base. Skill: `knowledge-extractor` (4 modules: agent review → classify → decontextualize → integrate).
 
+Quick and full runs with a reusable finding have a required final persistence gate. The command
+passes one structured record to `.claude/hooks/write-insight.cjs`; normal completion requires a
+`created`, `appended`, or `duplicate` receipt. The writer creates `.claude/insights/index.md` only
+on the first valid write, preserves prior bytes on append, and suppresses an exact normalized replay
+even when its render date changes. It then attempts an idempotent, best-effort `dz teach` projection;
+absence or failure never changes the Markdown receipt. `marker` and findings-free runs do not
+manufacture entries. The deterministic tests cover creation, append preservation, exact-repeat
+idempotence, and optional projection; they do not claim the text is meaningful.
+
 ---
 
 ## 💻 CLI Commands
@@ -641,7 +716,7 @@ Extract reusable patterns from a completed project into a knowledge base. Skill:
 | `update` | Upgrade files to new version (preserves customizations) | `0` ok, `1` if not installed |
 | `remove` | Delete package-tracked files | `0` ok, `1` if not installed |
 | `list` | List installed components with metadata | `0` |
-| `doctor` | Health check of pre-shipped contract + git PATH | `0` ok, `1` if anything broken |
+| `doctor` | Health check + informational recent fix/insight counts | `0` ok, `1` only if existing health checks find breakage |
 | `verify` | Pre-shipped + post-/replicate verification | `0` ok, `1` if pre-shipped contract violated |
 
 ### Global flags
@@ -732,6 +807,9 @@ Generates 5 SPARC docs in `docs/features/<feature>/`:
 - `04_refinement.md` — edge cases + error paths
 - `05_completion.md` — testing + deployment notes
 
+Before Phase 2, `/feature` runs the installed machine-key checker. Only exit `0` advances; exit `1`
+returns to PLAN with exact FR/NFR/AC gaps, while exit `2` stops on an unresolved role map or document.
+
 ### Phase 2 — VALIDATE (requirements-validator)
 
 Same swarm-of-5 as `/replicate` Phase 2. Verdict 🟢/🟡/🔴 with same retry logic.
@@ -752,7 +830,7 @@ Severity-classified findings. Critical (`blocker` | `high`) MUST be fixed.
 
 ### AUTO mode (called from /go or /run)
 
-- Phase 1: proceed if all docs exist
+- Phase 1: proceed only if all docs exist and the traceability checker exits `0`
 - Phase 2: proceed if 🟢 or 🟡; auto-retry once on 🔴
 - Phase 3: proceed if tests + lint + build green
 - Phase 4: auto-fix `high` if straightforward; halt on `blocker`
@@ -774,7 +852,7 @@ P-Replicator V1.5.x ● user │ Sonnet 4.7
 🚀 Pipeline   /<cmd> ▓▓▓░░░░ 50%  │ Phase: VALIDATE (2/4)  │ Last: /replicate
 🎯 Roadmap    [●●●○○○○○] mvp 3/8   │ Done 5/12  │ ▶ auth-jwt  │ Domain: banking
 📊 SPARC      ●11/11  │ 🟢 78/100  │ Plans ●3  │ ADRs ●2  │ Harvest 2026-05-05
-🛠️ Toolkit    Skills ●10/10 │ Cmds ●11/11 │ Agents ●4+3 │ Rules ●6+2 │ Hooks ●7/7
+🛠️ Toolkit    Skills ●10/10 │ Cmds ●11/11 │ Agents ●4+3 │ Rules ●9+2 │ Hooks ●9/9
 💡 Insights   ●12 (2026-05-06) │ Tests 85/85 ✓ │ MCP ●1/1 │ Settings ✓ │ 🧬 Keysarium ✓
 ```
 
@@ -810,16 +888,19 @@ For internals, see [admin guide](./README/eng/03_admin_guide.md#statusline--dash
 
 ## 🪝 Hooks System
 
-`p-replicator` ships **6 cross-platform Node scripts** in `.claude/hooks/`:
+`p-replicator` ships **10 cross-platform Node utilities** in `.claude/hooks/`. The Bash traceability
+gate described above remains a package script and is resolved directly by `/feature`; it is not a
+Claude Code hook.
 
 | Hook | Event | Purpose |
 |---|---|---|
-| `session-insights.cjs` | SessionStart | Inject 3 recent insights from `.claude/insights/index.md` to stdout (Claude Code captures into context) |
+| `session-insights.cjs` | SessionStart + UserPromptSubmit | Show the missing-carrier hint at start; at prompt time select armed dz recall or the local last-three fallback |
 | `autocommit-roadmap.cjs` | Stop | Auto-commit `.claude/feature-roadmap.json` if changed |
 | `autocommit-insights.cjs` | Stop | Auto-commit `.claude/insights/` if changed |
 | `autocommit-plans.cjs` | Stop | Auto-commit `docs/plans/` if changed |
 | `statusline.cjs` | (statusLine config) | Multi-line dashboard above the prompt |
 | `state-update.cjs` | (utility) | Argv-driven helper for writing `.claude/.p-replicator-state.json` |
+| `write-insight.cjs` | (utility, invoked by `/harvest`) | Establish Markdown, return `created`/`appended`/`duplicate`, then best-effort project the same record through dz |
 
 ### Cross-platform discipline
 
@@ -898,7 +979,14 @@ Pipeline commands optionally call this script (via Bash tool) so statusline show
 
 ### Insights system
 
-**Storage:** `.claude/insights/index.md` (markdown log).
+**Storage:** `.claude/insights/index.md` (Markdown source of truth). The writer persists it before
+an idempotent best-effort `dz teach` duplicate, so removing or breaking `.dz` cannot remove a record.
+
+`/myinsights` captures a record manually; quick/full `/harvest` uses the same carrier through the
+packaged writer. A fresh install intentionally has no `.claude/insights/` directory. The first valid
+write creates it; `init` does not pre-create an empty carrier, so doctor can keep distinguishing
+missing, existing-empty, and populated states. Until that first write, SessionStart prints one line:
+`инсайтов пока нет; /myinsights создаст первую запись`.
 
 **Entry format:**
 
@@ -927,7 +1015,28 @@ What fixed it (1-5 sentences with code if relevant).
 - ✅ `prisma-migration`, `postgres-timezone`, `docker-compose-network`
 - ❌ `bug`, `fix`, `important` (too generic — recall fails)
 
-**Auto-injection:** `SessionStart` hook (`session-insights.cjs`) reads top 3 recent entries to stdout, Claude Code injects into initial session context.
+**Prompt-time injection:** `UserPromptSubmit` passes the real prompt to `session-insights.cjs`. Only a
+successful, non-empty dz recall result from the insight domain suppresses local output. Absent,
+failing, or empty recall uses the local fallback (the last 3 Markdown entries); failure is named,
+absence and empty output are quiet, and one invocation never emits both sources. `SessionStart`
+retains only the missing-carrier hint above.
+
+### Doctor insight-flow observation
+
+Every `doctor` invocation measures one shared period covering the current date and the preceding two
+dates—three calendar days in the process's local timezone—and prints the period with both raw counts:
+`N fix commits and M insight records`.
+
+- Fix commits come from a fresh, bounded read of project git history and count only Conventional
+  Commit subjects beginning with `fix:` or `fix(scope):`.
+- Insight records come from fresh dated `## YYYY-MM-DD — ...` headings in
+  `.claude/insights/index.md`. A missing carrier is a measured count of zero.
+- If the project is not a git repository, has no readable history, or a required source is unreadable,
+  the line says `check NOT performed` and names the source instead of inventing a count.
+
+The observation is informational: it has no threshold, does not interpret the relationship between
+the counts, and does not change `doctor` exit status. Existing installation-health checks remain the
+only owners of exit `0` or `1`.
 
 ---
 
@@ -1001,6 +1110,14 @@ Default structure after `init`:
         ]
       }
     ],
+    "UserPromptSubmit": [
+      {
+        "matcher": "*",
+        "hooks": [
+          { "type": "command", "command": "node \"${CLAUDE_PROJECT_DIR}/.claude/hooks/session-insights.cjs\"", "timeout": 5 }
+        ]
+      }
+    ],
     "Stop": [
       {
         "matcher": "*",
@@ -1220,17 +1337,15 @@ npx @dzhechkov/p-replicator@latest init --force
 npx @dzhechkov/p-replicator verify
 ```
 
-### Insights aren't auto-injected into new sessions
+### Insights aren't injected after a prompt
 
 Checks:
 1. `.claude/insights/index.md` exists with entries?
-2. Hook works:
-   ```bash
-   node "${CLAUDE_PROJECT_DIR:-.}/.claude/hooks/session-insights.cjs"    # should print recent insights
-   ```
-3. SessionStart hook configured in `settings.json`?
+2. `UserPromptSubmit` is configured in `.claude/settings.json`?
+3. If dz recall fails, does the hook name degradation and show the local fallback?
+4. If dz is absent or returns empty, does the local fallback appear without a dz error?
 
-If all 3 OK but still nothing — Claude Code may cache. Restart `claude`.
+If all checks are OK but still nothing — Claude Code may cache settings. Restart `claude`.
 
 ### Statusline lags on every command
 
@@ -1296,17 +1411,18 @@ npx @dzhechkov/p-replicator verify
 
 <br>
 
-**Suite:** 105 tests, 36 suites, ~25 sec runtime.
+**Suite command:** `npm test` (plain Node test runner; never watch mode).
 
 | Layer | File | Coverage |
 |---|---|---|
-| **Unit** | `tests/unit/utils.test.js` (54 tests) | Pure functions: createManifest, mergeSettingsJson, removeOrphanHooks, getItemRelativePath, parseToolkit logic |
-| **E2E** | `tests/e2e/lifecycle.test.js` (48 tests) | Full CLI lifecycle, hooks installation, settings merge edge cases, statusline output, --feature-branches docs |
-| **Snapshot** | `tests/snapshot/templates.test.js` (3 tests) | SHA-256 baseline of all 115 files in `templates/` |
+| **Unit** | `tests/unit/*.test.js` | Pure utilities, role-map and traceability contracts, hook behavior, and document consistency |
+| **E2E** | `tests/e2e/*.test.js` | Full CLI lifecycle plus fresh-install execution of the exact `npm pack` insight writer artifact |
+| **Snapshot** | `tests/snapshot/templates.test.js` | SHA-256 baseline of package templates (140 file hashes, MEASURED — `npm run snapshot:baseline`) |
 
 **Meta-tests** verify consistency between documents:
 - `replicate-pipeline.md` mentions every pre-shipped command (no orphan in rule)
 - `replicate.md` Phase 3 doesn't claim "Generate `<pre-shipped>.md`" (no spec drift)
+- Negative/E2E fixtures live under `tests/fixtures/`; `files[]` ships `tests/`, so they are included in the npm package.
 
 **Snapshot baseline** regenerated via `npm run snapshot:baseline` after intentional template changes.
 
@@ -1466,7 +1582,7 @@ npm test
 
 ```bash
 npm run snapshot:baseline    # regenerate baseline if templates/ changed
-npm test                     # all 105 tests must pass
+npm test                     # settled suite: 396 pass + 3 intentional skips
 npm pack --dry-run           # verify tarball contents
 npm publish
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dzhechkov/p-replicator",
-  "version": "1.10.3",
+  "version": "1.12.0",
   "description": "P-Replicator — Claude Code toolkit for AI-assisted product development (Vibe Coding). Full /replicate pipeline, 10 modular skills (880K+ chars), /harvest knowledge extraction, swarm agents, quality gates, security patterns, cross-project learning.",
   "main": "src/cli.js",
   "bin": {
@@ -9,6 +9,7 @@
   "files": [
     "bin/",
     "src/",
+    "scripts/check-pipeline-gaps.sh",
     "templates/",
     "tests/",
     "README/",
@@ -18,6 +19,15 @@
     ".dz-manifest.json",
     "sbom.json"
   ],
+  "scripts": {
+    "prepublishOnly": "node --test tests/snapshot/templates.test.js && node ../../../scripts/prepublish-gate.mjs",
+    "test": "node --test tests/unit/honest-failure-rules.test.js tests/unit/detection-ladder-contract.test.js tests/unit/detection-ladder-registry.test.js tests/unit/utils.test.js tests/unit/adr-scanner-contract.test.js tests/unit/sparc-reconciliation.test.js tests/unit/pipeline-file-ownership.test.js tests/unit/validation-gate-teeth.test.js tests/unit/hooks-project-anchored.test.js tests/unit/insights-dz-delegation.test.js tests/unit/statusline-two-roots.test.js tests/unit/external-dependency-check.test.js tests/unit/spec-pseudocode-traceability.test.js tests/unit/sync-templates-guard.test.js tests/unit/db-port-rule.test.js tests/unit/roadmap-one-schema.test.js tests/unit/hooks-report-failures.test.js tests/unit/growth-module-b2b-gate.test.js tests/unit/detect-parse-anchor.test.js tests/unit/statusline-honest-labels.test.js tests/unit/autocommit-deletion.test.js tests/unit/check-ports.test.js tests/unit/doctor-insight-flow.test.js tests/unit/adr-decision-coverage.test.js tests/unit/growth-requirements-bridge.test.js tests/unit/check-growth-trace.test.js tests/unit/growth-gate-conditional.test.js tests/unit/module-copy-identity.test.js tests/unit/growth-axes-and-compliance.test.js tests/unit/skill-paths-prebaked.test.js tests/unit/check-docs-complete.test.js tests/unit/absence-is-not-emptiness.test.js tests/unit/guard-forms.test.js tests/unit/generated-guard-templates.test.js tests/unit/shipped-suite-context.test.js tests/unit/assess-scripts.test.js tests/unit/insights-docs-tell-the-truth.test.js tests/unit/insights-writer.test.js tests/unit/check-pipeline-gaps.test.js tests/unit/traceability-machine-ids.test.js tests/unit/traceability-negative-fixture.test.js tests/e2e/lifecycle.test.js tests/e2e/packed-insights-writer.test.js tests/snapshot/templates.test.js",
+    "test:unit": "node --test tests/unit/honest-failure-rules.test.js tests/unit/detection-ladder-contract.test.js tests/unit/detection-ladder-registry.test.js tests/unit/utils.test.js tests/unit/adr-scanner-contract.test.js tests/unit/sparc-reconciliation.test.js tests/unit/pipeline-file-ownership.test.js tests/unit/validation-gate-teeth.test.js tests/unit/hooks-project-anchored.test.js tests/unit/insights-dz-delegation.test.js tests/unit/statusline-two-roots.test.js tests/unit/external-dependency-check.test.js tests/unit/spec-pseudocode-traceability.test.js tests/unit/sync-templates-guard.test.js tests/unit/db-port-rule.test.js tests/unit/roadmap-one-schema.test.js tests/unit/hooks-report-failures.test.js tests/unit/growth-module-b2b-gate.test.js tests/unit/detect-parse-anchor.test.js tests/unit/statusline-honest-labels.test.js tests/unit/autocommit-deletion.test.js tests/unit/check-ports.test.js tests/unit/doctor-insight-flow.test.js tests/unit/adr-decision-coverage.test.js tests/unit/growth-requirements-bridge.test.js tests/unit/check-growth-trace.test.js tests/unit/growth-gate-conditional.test.js tests/unit/module-copy-identity.test.js tests/unit/growth-axes-and-compliance.test.js tests/unit/skill-paths-prebaked.test.js tests/unit/check-docs-complete.test.js tests/unit/absence-is-not-emptiness.test.js tests/unit/guard-forms.test.js tests/unit/generated-guard-templates.test.js tests/unit/shipped-suite-context.test.js tests/unit/assess-scripts.test.js tests/unit/insights-docs-tell-the-truth.test.js tests/unit/insights-writer.test.js tests/unit/check-pipeline-gaps.test.js tests/unit/traceability-machine-ids.test.js tests/unit/traceability-negative-fixture.test.js",
+    "test:e2e": "node --test tests/e2e/lifecycle.test.js tests/e2e/packed-insights-writer.test.js",
+    "test:snapshot": "node --test tests/snapshot/templates.test.js",
+    "test:doctor": "node bin/cli.js doctor",
+    "snapshot:baseline": "node tests/snapshot/update-baseline.js"
+  },
   "keywords": [
     "claude",
     "claude-code",
@@ -53,12 +63,12 @@
   },
   "repository": {
     "type": "git",
-    "url": "https://github.com/djd1m/dz-harness-hub.git",
+    "url": "git+https://github.com/djd1m/dz-harness.git",
     "directory": "packages/@dzhechkov/p-replicator"
   },
-  "homepage": "https://github.com/djd1m/dz-harness-hub/tree/main/packages/@dzhechkov/p-replicator#readme",
+  "homepage": "https://github.com/djd1m/dz-harness/tree/main/packages/@dzhechkov/p-replicator#readme",
   "bugs": {
-    "url": "https://github.com/djd1m/dz-harness-hub/issues"
+    "url": "https://github.com/djd1m/dz-harness/issues"
   },
   "peerDependencies": {
     "@dzhechkov/keysarium-core": "^1.1.0"
@@ -70,13 +80,5 @@
   },
   "publishConfig": {
     "access": "public"
-  },
-  "scripts": {
-    "test": "node --test tests/unit/utils.test.js tests/unit/adr-scanner-contract.test.js tests/unit/sparc-reconciliation.test.js tests/unit/pipeline-file-ownership.test.js tests/unit/validation-gate-teeth.test.js tests/unit/hooks-project-anchored.test.js tests/unit/statusline-two-roots.test.js tests/unit/external-dependency-check.test.js tests/unit/spec-pseudocode-traceability.test.js tests/unit/sync-templates-guard.test.js tests/unit/db-port-rule.test.js tests/unit/roadmap-one-schema.test.js tests/unit/hooks-report-failures.test.js tests/unit/growth-module-b2b-gate.test.js tests/unit/detect-parse-anchor.test.js tests/unit/statusline-honest-labels.test.js tests/unit/autocommit-deletion.test.js tests/unit/check-ports.test.js tests/unit/adr-decision-coverage.test.js tests/unit/growth-requirements-bridge.test.js tests/unit/check-growth-trace.test.js tests/unit/growth-gate-conditional.test.js tests/unit/module-copy-identity.test.js tests/unit/growth-axes-and-compliance.test.js tests/unit/skill-paths-prebaked.test.js tests/unit/check-docs-complete.test.js tests/unit/absence-is-not-emptiness.test.js tests/unit/guard-forms.test.js tests/unit/generated-guard-templates.test.js tests/unit/shipped-suite-context.test.js tests/unit/assess-scripts.test.js tests/unit/insights-docs-tell-the-truth.test.js tests/e2e/lifecycle.test.js tests/snapshot/templates.test.js",
-    "test:unit": "node --test tests/unit/utils.test.js tests/unit/adr-scanner-contract.test.js tests/unit/sparc-reconciliation.test.js tests/unit/pipeline-file-ownership.test.js tests/unit/validation-gate-teeth.test.js tests/unit/hooks-project-anchored.test.js tests/unit/statusline-two-roots.test.js tests/unit/external-dependency-check.test.js tests/unit/spec-pseudocode-traceability.test.js tests/unit/sync-templates-guard.test.js tests/unit/db-port-rule.test.js tests/unit/roadmap-one-schema.test.js tests/unit/hooks-report-failures.test.js tests/unit/growth-module-b2b-gate.test.js tests/unit/detect-parse-anchor.test.js tests/unit/statusline-honest-labels.test.js tests/unit/autocommit-deletion.test.js tests/unit/check-ports.test.js tests/unit/adr-decision-coverage.test.js tests/unit/growth-requirements-bridge.test.js tests/unit/check-growth-trace.test.js tests/unit/growth-gate-conditional.test.js tests/unit/module-copy-identity.test.js tests/unit/growth-axes-and-compliance.test.js tests/unit/skill-paths-prebaked.test.js tests/unit/check-docs-complete.test.js tests/unit/absence-is-not-emptiness.test.js tests/unit/guard-forms.test.js tests/unit/generated-guard-templates.test.js tests/unit/shipped-suite-context.test.js tests/unit/assess-scripts.test.js tests/unit/insights-docs-tell-the-truth.test.js",
-    "test:e2e": "node --test tests/e2e/lifecycle.test.js",
-    "test:snapshot": "node --test tests/snapshot/templates.test.js",
-    "test:doctor": "node bin/cli.js doctor",
-    "snapshot:baseline": "node tests/snapshot/update-baseline.js"
   }
-}
+}