@dzhechkov/p-replicator 1.12.0 → 1.13.2

package/src/utils.js

@@ -354,7 +354,22 @@ const COMPONENTS = {
       'write-insight':       'Validate and append one harvest insight to the project Markdown carrier',
       'check-ports':              'Enforce docker-ports Правило №0 against a real compose (invoke deliberately; exits 0/1/2)',
       'check-growth-trace':       'Did the M5 growth seed reach docs/Specification.md (invoke deliberately; exits 0/1/2)',
+      'check-look-trace':         'Did the Phase-0.5 source-look seed reach docs/Specification.md (invoke deliberately; exits 0/1/2)',
+      'check-look-origin':        'Did a third-party-analysis HYPOTHESIS row reach Specification.md without dated live confirmation (invoke deliberately; exits 0/1/2)',
+      'check-review-contract':    'Does review-report.md answer every AC id, disclose the reviewer family and name the spec revision it judged (exits 0/1/2)',
+      'capture-source-path':      'Phase-0.5 «путь» axis: click through the source product in a browser and emit FR-LOOK rows (external Playwright; exits 0/1/2)',
       'check-docs-complete':      'Are Phase-1 documents written and placeholder-free, before the Phase-2 swarm (invoke deliberately; exits 0/1/2)',
+      'check-swarm-receipts':     'Did every parallel work unit deliver its named terminal file, before the coordinator aggregates (invoke deliberately; exits 0/1/2)',
+      'check-embed-contract':     'Was the embeddable widget checked on a FOREIGN origin — cross-origin, style leakage, host CSP (invoke deliberately; exits 0/1/2)',
+      'check-webhook-contract':   'Is the incoming webhook signed, deduplicated by a NAMED repeat key with atomic exclusion, and safe against reordering (invoke deliberately; exits 0/1/2)',
+      'check-job-contract':       'Does long-running work carry a handle issued before the work, three distinguishable states and a retry that continues (invoke deliberately; exits 0/1/2)',
+      'check-model-cost':         'Does every external model call name a ceiling that can BIND — a number, per user and per day, refusing at the limit (invoke deliberately; exits 0/1/2)',
+      'check-canon':              'Before a WRITING fan-out: is the shared canon named, pinned by sha256 and free of colliding ordinals and self-contradicting lists (invoke deliberately; exits 0/1/2)',
+      'check-file-ownership':     'Before a WRITING fan-out: does every written file have exactly one writer — coordinator included — and does a file born by a SPLIT get its owner at creation (invoke deliberately; exits 0/1/2)',
+      'check-source-version':     'Before a merge: does every edit and every verdict declare the sha256 of the source it was built on, and does it still match (invoke deliberately; exits 0/1/2)',
+      'check-handoff-manifest':   'Phase 0 to Phase 1: did every enumerated discovery output get an answer — cited by id, or rejected with a reason (invoke deliberately; exits 0/1/2)',
+      'check-external-deps':      'Does the external-dependency inventory EXIST and carry a verdict per row — an absent section is never «no dependencies» (invoke deliberately; exits 0/1/2)',
+      'check-metric-source':      'Does every success metric name WHERE its value comes from, from a closed list, and does an external-API metric have its inventory row (invoke deliberately; exits 0/1/2)',
     },
   },
   // ─── Project-generated groups (created by /replicate Phase 3) ───────────
@@ -498,6 +513,19 @@ function removeOrphanHooks(existing, oldTemplate, newTemplate) {
   return cleaned;
 }
 
+/**
+ * Canonical form of a hook command for DEDUP ONLY (backlog a1ef0e41 — MEASURED: a user who
+ * hand-rewrote `$CLAUDE_PROJECT_DIR` into `${CLAUDE_PROJECT_DIR}` got every event hook DOUBLED on
+ * the next update, because the byte-equality Set saw two different strings for one command).
+ * Both spellings expand identically in sh, so for identity purposes they ARE the same command:
+ * `${VAR}` collapses to `$VAR`, and whitespace runs collapse to one space. The STORED command is
+ * never rewritten — the user's own spelling always survives; only the comparison key changes.
+ */
+function canonicalHookCommand(command) {
+  if (typeof command !== 'string') return command;
+  return command.replace(/\$\{([A-Za-z_][A-Za-z0-9_]*)\}/g, '$$$1').replace(/\s+/g, ' ').trim();
+}
+
 function mergeHookMatchers(existing, template) {
   // Clone the existing array; we'll mutate per-entry hook arrays via reference.
   const result = existing.map((m) => ({ ...m, hooks: [...(m.hooks || [])] }));
@@ -508,10 +536,12 @@ function mergeHookMatchers(existing, template) {
       result.push({ ...tplEntry, hooks: [...(tplEntry.hooks || [])] });
       continue;
     }
-    // Same matcher — append template hooks not already present (compare by command)
-    const existingCmds = new Set(target.hooks.map((h) => h.command));
+    // Same matcher — append template hooks not already present. Identity is the CANONICAL
+    // command (see canonicalHookCommand), so a user's `${VAR}` respelling of a shipped `$VAR`
+    // hook no longer reads as a different hook and doubles on every update.
+    const existingCmds = new Set(target.hooks.map((h) => canonicalHookCommand(h.command)));
     for (const tplHook of tplEntry.hooks || []) {
-      if (!existingCmds.has(tplHook.command)) {
+      if (!existingCmds.has(canonicalHookCommand(tplHook.command))) {
         target.hooks.push(tplHook);
       }
     }

package/templates/.claude/agents/product-discoverer.md

@@ -46,8 +46,46 @@ Product Discovery Brief — structured markdown passed as pre-filled context to
 
 ### Key Insights for PRD
 [Top 3-5 insights that should inform product planning]
+
+## Манифест передачи
+
+**Фаза 0 выполнена:** да
+**Проверка манифеста:** ВЫПОЛНЕНА
+**Причина:** —
+
+| Выход | Идентификатор | Модуль |
+|---|---|---|
+| [what this run actually produced] | PD-INSIGHT-001 | M5 |
 ```
 
+### The manifest is REQUIRED, and it is the last thing written
+
+The brief's six sections are passed onward through a CLOSED list of four fields
+(`target_segments`, `key_competitors`, `differentiation`, `monetization`). Two of the six therefore
+have no field at all — «Key Insights for PRD» has none, and «Growth Channels» travels only through
+the separate `FR-GROWTH` seed. The artifact is written, it is on disk, and the next phase has no
+input through which it could reach a decision: «used» and «silently dropped» look identical from
+every side, because nobody is obliged to answer by list.
+
+The manifest is that list. Three rules, and each of them is what makes it checkable rather than
+ceremonial:
+
+1. **Only ENUMERABLE outputs of the REAL run**, each with a stable identifier `PD-WORD-nnn`
+   (uppercase, three digits, never reused). Free prose cannot be answered by list, and answering by
+   list is the entire cure.
+2. **A module that did not run owes NOTHING.** Do not invent rows for modules you skipped — a
+   manifest padded to look complete is worse than a short one, because it makes the check pass while
+   describing work nobody did.
+3. **Phase 1 answers every row**: cite the id in a Phase-1 document, or reject it WITH A REASON in
+   the same line. Silence is neither, and it is the only outcome the check refuses to interpret
+   charitably.
+
+Deterministic half: `node .claude/hooks/check-handoff-manifest.cjs .` — `0` every output answered ·
+`1` a defect is PROVEN and NAMED (an output nobody answered for, a rejection with no reason, an
+empty manifest) · `2` THE CHECK DID NOT RUN (no brief — Phase 0 never ran, `--from-docs` skips it —
+no manifest section, no Phase-1 documents, a malformed or duplicated id, or the honest «НЕ
+ВЫПОЛНЕНА» with a reason). Exit `2` never means "all clear".
+
 ## Anti-Hallucination Rules
 
 - Search first — never answer from memory for facts

package/templates/.claude/agents/replicate-coordinator.md

@@ -8,9 +8,19 @@ Activated automatically by the `/replicate` command. Do NOT invoke directly.
 
 ## Responsibilities
 
-1. **Phase Management** — ensure correct phase sequence (0 → 1 → 2 → 3 → 4)
+1. **Phase Management** — ensure correct phase sequence (0 → 0.5 → 1 → 2 → 3 → 4).
+   Phase 0 is OPTIONAL and is skipped entirely by the `--from-docs` / `--skip-discovery` entry;
+   **Phase 0.5 (Source Product Profile) is MANDATORY and runs in every case**, which is why it is a
+   separate phase rather than a module inside Phase 0.
 2. **Context Passing** — carry forward outputs between phases:
    - Phase 0 → Phase 1: Product Discovery Brief
+   - Phase 0.5 → Phase 1: Source Product Profile (`docs/source-product-profile.md`) — a capture
+     status PER AXIS (`облик` and `путь` each answer `СНЯТ` / `НЕ ИЗМЕРЕНО` + reason /
+     `ИСТОЧНИКА НЕТ`, because they fail apart) plus the `FR-LOOK-nnn` seed rows of ONE family. A
+     `СНЯТ` profile's palette SUPERSEDES the industry palette of `025-cjm-prototype.md`; in the
+     other two states that table is a LABELLED fallback. The `путь` axis is captured by
+     `.claude/hooks/capture-source-path.cjs` (browser click-through; Playwright is an external
+     prerequisite, and its absence is the outcome `no-browser`, never a stalled run)
    - Phase 1 → Phase 2: 11 SPARC documents
    - Phase 2 → Phase 3: Validated docs + test-scenarios
    - Phase 3 → Phase 4: Complete toolkit

package/templates/.claude/commands/feature.md

@@ -133,6 +133,17 @@ Run validation against INVEST + SMART + BDD scenario completeness.
 
 Output: `docs/features/<feature>/validation-report.md`
 
+The report carries the `Spec revision:` line and the `## Criterion scenarios` table (AC id → BDD
+scenario) in the exact format of
+`.claude/skills/requirements-validator/references/feature-report-contracts.md`. Then run:
+
+```bash
+bash "$CHECK_PIPELINE_GAPS" "${CLAUDE_PROJECT_DIR:-.}" --report-revision --criterion-scenarios
+```
+
+Same exit semantics as the Phase 1 gate: `0` advances; `1` (stale revision, AC id without a scenario
+row) returns to Phase 2; `2` stops.
+
 ### Phase 3: IMPLEMENT (parallel agents)
 
 1. Read SPARC docs from Phase 1
@@ -143,22 +154,74 @@ Output: `docs/features/<feature>/validation-report.md`
 6. Coordinator validates every trace before merge/integration
 7. Run full test suite
 
+#### Canon before dispatch (required)
+
+**The canon MUST be frozen BEFORE dispatch.** Parallel units are N writers deriving names and
+numbers from one source; the collision exists ONLY IN THE UNION, so no worker can see it and no
+receipt can catch it. The coordinator records `docs/dispatch-plan.md` — the canon path and its
+sha256 — or runs the units sequentially.
+
+The same plan MUST assign OWNERSHIP: exactly one writer per file, the coordinator included, and a
+file born by SPLITTING another gets its owner AT CREATION — ownership never travels by itself.
+
+Every EDIT and every VERDICT MUST declare the sha256 of the source it was built on; a
+mismatch with the live file is a refusal WITHOUT mutation — a read copy is a snapshot of the moment
+of reading, not of the file.
+
+Field forms and closed value lists are in the checkers' headers:
+
+```bash
+node .claude/hooks/check-canon.cjs .
+node .claude/hooks/check-file-ownership.cjs .
+node .claude/hooks/check-source-version.cjs .
+```
+
+`0` frozen and intact · `1` a defect is PROVEN and named · `2` **THE CHECK DID NOT RUN**, which is
+never "all clear".
+
 #### Positive file receipt (required)
 
 Before dispatch, allocate one `RUN_ID` and, for every independent unit, a unique `WORK_UNIT_ID`.
 Resolve `TRACE_PATH` to an absolute path unique to `(RUN_ID, WORK_UNIT_ID)` and pass both fields.
 Require the worker to write a substantive body ending in `Status: completed` or `Status: failed` to
-`TRACE_PATH` before returning a one-line pointer. Before integration, verify each path is a regular
-non-symlink file, non-whitespace, post-launch, and terminal. Narrative output or silence is not a
-receipt. Name missing, stale, partial, unreadable, duplicate, failed, dead-PID, or probe-error units
-and refuse merge/completion unless every required receipt is valid and completed. See
-`.claude/rules/swarm-file-evidence.md` for mechanics and the bounded non-atomic-write exception.
+`TRACE_PATH` before its one-line pointer. Before integration, MUST verify a regular, non-symlink,
+substantive, post-launch file with a terminal status. Narrative/chat/silence is never a receipt; any
+invalid receipt MUST block merge/completion. Full rule and bounded exception:
+`.claude/rules/swarm-file-evidence.md`.
+
+#### Threshold tests pin the number (layer-2 rule)
+
+A test of a THRESHOLD asserts the literal number; a test of a DERIVED value calls the production
+implementation. A test that computes its expectation from the production constant is green for any
+value and proves nothing.
+
+#### Blocking criterion-coverage gate
+
+`05_completion.md` MUST carry the `## Criterion coverage` table (AC id → test file → test title; format
+in `feature-report-contracts.md`). At the end of Phase 3 run:
+
+```bash
+bash "$CHECK_PIPELINE_GAPS" "${CLAUDE_PROJECT_DIR:-.}" --completion
+```
+
+`0` advances; `1` (an AC without a test, a row whose file or title does not exist) returns to
+Phase 3; `2` stops. Never downgrade either non-zero status to a warning.
 
 ### Phase 4: REVIEW (brutal-honesty-review)
 
 Read: `.claude/skills/brutal-honesty-review/SKILL.md`
 
-Findings classified by severity. Critical (blocker | high) MUST be fixed.
+Specification contract: the review receives `01_specification.md` + `validation-report.md` (a review
+not given the specification is incomplete by construction and says so) and writes
+`docs/features/<feature>/review-report.md` — `Reviewer family:` (disclosure) and `Spec revision:` in the
+first 20 lines, an AC-by-AC `## Spec conformance` table — per `feature-report-contracts.md`. Then run:
+
+```bash
+node "${CLAUDE_PROJECT_DIR:-.}/.claude/hooks/check-review-contract.cjs" "${CLAUDE_PROJECT_DIR:-.}" "<feature>"
+```
+
+`0` advances; `1` (named contract gaps) returns to Phase 4; `2` stops. Findings classified by
+severity. Critical (blocker | high) MUST be fixed.
 
 ## Final Steps
 
@@ -172,8 +235,11 @@ Skip per-phase user confirmations. Auto-decisions:
 - Phase 1: proceed if all docs exist
 - Phase 1 traceability: proceed only when `check-pipeline-gaps.sh` exits `0`; preserve exit `1`/`2`
 - Phase 2: proceed if 🟢 or 🟡; auto-retry once on 🔴
+- Phase 2 report revision + criterion scenarios: proceed only when `--report-revision --criterion-scenarios` exits `0`; preserve exit `1`/`2`
 - Phase 3: proceed if tests + lint + build green
+- Phase 3 criterion coverage: proceed only when `--completion` exits `0`; preserve exit `1`/`2`
 - Phase 4: auto-fix `high` if straightforward; halt on `blocker`
+- Phase 4 review contract: proceed only when `check-review-contract.cjs` exits `0`; preserve exit `1`/`2`
 
 ## Related
 

package/templates/.claude/commands/go.md

@@ -75,14 +75,12 @@ Same as `/feature` but with idea2prd-manual + DDD coherence + ADR consistency
 
 ### Delegated parallel-work receipt (required)
 
-For any selected pipeline that dispatches parallel work, allocate one `RUN_ID`, a unique
-`WORK_UNIT_ID`, and an absolute `TRACE_PATH` per unit. Require each worker to write a substantive body
-ending in `Status: completed` or `Status: failed` to `TRACE_PATH` before its one-line pointer. Before
-the routed pipeline reports merge, synthesis, or completion, verify each path is a regular non-symlink
-file, non-whitespace, post-launch, and terminal. Narrative output or silence is not a receipt. Name
-missing, stale, partial, unreadable, duplicate, failed, dead-PID, or probe-error units and refuse
-aggregation/completion unless every required receipt is valid and completed. The selected pipeline
-owns the paths; this router never substitutes its own report. See `.claude/rules/swarm-file-evidence.md`.
+For parallel work, assign each unit a unique `WORK_UNIT_ID` and unique absolute `TRACE_PATH`. The worker
+MUST write a substantive body ending in `Status: completed` or `Status: failed` to `TRACE_PATH` before
+its one-line pointer. Before merge/synthesis/completion, the selected pipeline MUST verify a regular,
+non-symlink, substantive, post-launch file with a terminal status. Narrative/chat/silence is never a
+receipt; any invalid receipt MUST block merge/completion, and this router never substitutes its report.
+Full rule: `.claude/rules/swarm-file-evidence.md`.
 
 ## Step 6: Post-Implementation
 

package/templates/.claude/commands/harvest.md

@@ -55,13 +55,11 @@ Gate 5: PERSIST INSIGHT — quick/full must receive a valid writer receipt befor
 
 ### Phase 1 positive file receipts (required)
 
-Before the five-agent dispatch, allocate one `RUN_ID`, then assign every perspective a unique
-`WORK_UNIT_ID` and absolute `TRACE_PATH`. Require each agent to write a substantive body ending in
-`Status: completed` or `Status: failed` to `TRACE_PATH` before returning a one-line pointer. Before
-classification or synthesis, verify every path is a regular non-symlink file, non-whitespace,
-post-launch, and terminal. Narrative output or silence is not a receipt. Name missing, stale, partial,
-unreadable, duplicate, failed, dead-PID, or probe-error perspectives and refuse harvest completion
-unless every required receipt is valid and completed. See `.claude/rules/swarm-file-evidence.md`.
+Assign each perspective a unique `WORK_UNIT_ID` and unique absolute `TRACE_PATH`. Its agent MUST write
+a substantive body ending in `Status: completed` or `Status: failed` to `TRACE_PATH` before its one-line
+pointer. Before classification/synthesis, verify a regular, non-symlink, substantive, post-launch file
+with a terminal status. Narrative/chat/silence is never a receipt; any invalid receipt MUST block
+harvest completion. Full rule: `.claude/rules/swarm-file-evidence.md`.
 
 ## REQUIRED INSIGHT PERSISTENCE GATE (quick/full only)
 

package/templates/.claude/commands/replicate.md

@@ -31,6 +31,7 @@ All skills are available locally. Read their SKILL.md when needed:
 | Skill | Path | Phase |
 |-------|------|-------|
 | reverse-engineering-unicorn | `.claude/skills/reverse-engineering-unicorn/SKILL.md` | Phase 0 |
+| clone-website *(EXTERNAL — not pre-shipped)* | `.claude/skills/clone-website/SKILL.md` — install `@dzhechkov/skills-website-cloner` | Phase 0.5 (recon-only) |
 | sparc-prd-mini | `.claude/skills/sparc-prd-mini/SKILL.md` | Phase 1 |
 | explore | `.claude/skills/explore/SKILL.md` | Phase 1 (dependency) |
 | goap-research-ed25519 | `.claude/skills/goap-research-ed25519/SKILL.md` | Phase 1 (dependency) |
@@ -48,11 +49,13 @@ All skills are available locally. Read their SKILL.md when needed:
 ## Pipeline
 
 ```
-INPUT → [PRODUCT DISCOVERY] → PLANNING → VALIDATION → TOOLKIT → FINALIZE
-         (optional)            sparc-prd   requirements  cc-toolkit  commit
-                               -mini       -validator    -generator  & report
+INPUT → [PRODUCT DISCOVERY] → SOURCE PRODUCT → PLANNING → VALIDATION → TOOLKIT → FINALIZE
+         (optional)            PROFILE          sparc-prd   requirements  cc-toolkit  commit
+                               (ALWAYS)         -mini       -validator    -generator  & report
 ```
 
+Фаза 0 пропускается входом `--from-docs`; **Фаза 0.5 выполняется всегда** — потому и отдельная.
+
 **Note:** sparc-prd-mini v2 already includes Explore, Research, and Solve phases
 internally via skill references. The coordinator does NOT duplicate these phases.
 
@@ -80,17 +83,13 @@ but distinct from generated SPARC outputs.
 ### Modified pipeline flow when triggered
 
 - **Phase 0** (Product Discovery): SKIPPED entirely (no reverse-engineering-unicorn invocation)
-- **Phase 1** (sparc-prd-mini): MODIFIED
-  - Run in **AUTO mode** — do NOT ask interactive clarification questions
-  - SKIP internal sub-phases Explore / Research / Solve (their job is to
-    generate the answers that already exist in user docs)
-  - READ all files in user-provided path as pre-filled context
-  - Generate the 11 standardized SPARC documents in `docs/`, mapping content
-    from existing docs to appropriate slots (PRD, Solution_Strategy,
-    Specification, Pseudocode, Architecture, Refinement, Completion,
-    Research_Findings, Final_Summary, C4_Diagrams, ADR)
-  - For SPARC slots without source content in existing docs, mark with a
-    `[GAP: needs <description>]` placeholder rather than asking the user
+- **Phase 0.5** (Source Product Profile): **RUNS — this entry does NOT skip it**; the skip is Phase 0
+  alone, and a project arriving with someone else's docs is usually a replication. Where those docs
+  describe the source, record `СНЯТ` from them; where they do not, `НЕ ИЗМЕРЕНО` with a reason.
+- **Phase 1** (sparc-prd-mini): MODIFIED — **AUTO mode** (no interactive questions); SKIP
+  Explore/Research/Solve (they generate answers the user docs already hold); READ the user path as
+  pre-filled context; generate the 11 SPARC documents in `docs/`, mapping existing content to slots;
+  a slot with no source content gets `[GAP: needs <description>]` instead of a question
 - **Phase 2** (validation): runs UNCHANGED (validates the generated SPARC docs)
 - **Phase 3** (toolkit generation): runs UNCHANGED
 - **Phase 4** (finalize): runs UNCHANGED
@@ -142,7 +141,7 @@ above, but applies to ad-hoc feature additions rather than full project bootstra
 
 ### Start
 
-1. Briefly explain the phases (4 main + 1 optional)
+1. Briefly explain the phases (4 main + 1 optional Phase 0 + the mandatory Phase 0.5)
 2. Mention the target architecture (distributed monolith + Docker на VPS)
 3. Determine project type → is Product Discovery needed?
 4. Begin with the relevant phase
@@ -207,6 +206,106 @@ project has no growth requirements, and no consumer may read it that way.
 ═══════════════════════════════════════════════════════════════
 ```
 
+### Phase 0.5: SOURCE PRODUCT PROFILE (обязательная — выполняется ВСЕГДА)
+
+Когда проект воспроизводит существующий продукт, его ОБЛИК — палитра, типографика, плотность,
+компоновка экранов, порядок шагов — сердцевина задачи, а не приятность. Все шесть модулей Фазы 0
+разбирают бизнес, а палитру `025-cjm-prototype.md` НАЗНАЧАЛ по отрасли: конвейер, чья задача
+воспроизвести продукт, выдумывал ему внешность.
+
+**Почему ОТДЕЛЬНАЯ фаза, а не модуль Фазы 0.** Вход `--from-docs` / `--skip-discovery` пропускает
+Фазу 0 целиком. Модуль внутри неё выключился бы ровно для проектов с чужой документацией — то есть
+чаще всего именно для клонов. Поэтому фаза стоит ПОСЛЕ чекпоинта Фазы 0 и от него не зависит.
+
+**Съёмка — навык `clone-website` из ОТДЕЛЬНОГО пакета
+[`@dzhechkov/skills-website-cloner`](https://www.npmjs.com/package/@dzhechkov/skills-website-cloner),
+режим только разведка. ВЫЗЫВАЕТСЯ, НЕ КОПИРУЕТСЯ** — вендорить его сюда запрещено (ADR-0001 +
+`sources.json`): `npx @dzhechkov/skills-website-cloner init`. Навыка нет или браузерный MCP
+недоступен → исход `НЕ ИЗМЕРЕНО (no-browser-mcp)`; фаза всё равно выполняется, конвейер не встаёт.
+
+**Артефакт `docs/source-product-profile.md` — пишется ВСЕГДА, во всех трёх исходах:**
+
+```markdown
+**Источник:** Senja — https://senja.io   (либо `нет`)
+**Статус съёмки:** СНЯТ                  (ось «облик»; ровно одно: СНЯТ | НЕ ИЗМЕРЕНО | ИСТОЧНИКА НЕТ)
+**Причина:** —                           (обязательна при НЕ ИЗМЕРЕНО, из закрытого списка ниже)
+**Статус съёмки (путь):** СНЯТ           (ось «путь»; обязательна, когда строк оси «путь» НЕТ)
+**Причина (путь):** —                    (обязательна при НЕ ИЗМЕРЕНО оси «путь»)
+**Происхождение:** прокликано            (закрытый список: прокликано | сторонний-разбор | вручную | не снято)
+**Источник разбора:** —                  (обязательны при сторонний-разбор; дата — из разметки
+**Дата стороннего снимка:** —             источника, не из пересказа)
+
+## 🎨 Look Requirements Seed
+
+| ID | Обязательство | Ось | Источник-экран | Уверенность | Статус (ЧЕРНОВИК \| ГИПОТЕЗА \| ПОДТВЕРЖДЕНО \| УСТАРЕЛО) |
+|----|---|---|---|---|---|
+| FR-LOOK-001 | [что обязаны воспроизвести] | облик | [URL/скриншот] | [как измерено] | ЧЕРНОВИК |
+```
+
+Закрытый список причин, каждая означает СВОЙ ремонт: `no-browser-mcp` · `no-browser` ·
+`unreachable` · `auth-required` · `out-of-scope` · `bot-protected` · `timeout` ·
+`robots-disallowed`.
+
+`FR-LOOK-<nnn>` — ОДНО семейство: три цифры, по порядку, номер не переиспользуется. Ось (`облик` —
+что видно; `путь` — в каком порядке идут экраны) это КОЛОНКА, а не второе пространство имён: два
+семейства пришлось бы держать в согласии, одно с колонкой — нет. Полные правила строки и то, что
+именно считается заполненной строкой, — в шапке `.claude/hooks/check-look-trace.cjs`.
+
+**Две оси отвечают ПОРОЗНЬ, потому что и отказывают порознь:** лендинг снимается, а прокликивание
+упирается в 403 — один общий статус обязан был бы соврать про одну из осей. Строки оси «путь» и
+есть её ответ; объявление `**Статус съёмки (путь):**` требуется, только когда таких строк НЕТ.
+
+**Инструмент оси «путь» — прокликивание браузером:**
+
+```bash
+node .claude/hooks/capture-source-path.cjs <url> --max-pages 5 --delay-ms 1500
+```
+
+`0` снято, строки `FR-LOOK-nnn` с осью `путь` на stdout · `1` источник открылся, перехода нет
+(одноэкранный продукт — законный `ИСТОЧНИКА НЕТ` для этой оси) · `2` НЕ ИЗМЕРЕНО с причиной из
+списка. Playwright — ВНЕШНЕЕ предусловие (у пакета ноль зависимостей): нет его → честный
+`no-browser`, конвейер не встаёт. Границы съёмки — в `replicate-pipeline.md`, раздел Фазы 0.5;
+они не пожелание, а условие законности.
+
+**ТРИ исхода, и третий — тот, ради которого фаза написана именно так:**
+
+| Исход | Когда | Откуда палитра |
+|---|---|---|
+| `СНЯТ` | облик собран | из источника; отраслевая таблица `025` НЕ применяется |
+| `НЕ ИЗМЕРЕНО` | источник НАЗВАН, снять не удалось (причина из списка) | отраслевая, ПОДПИСАННАЯ как фолбэк |
+| `ИСТОЧНИКА НЕТ` | проект ничего не воспроизводит | отраслевая, ПОДПИСАННАЯ как фолбэк |
+
+Правило `honest-configuration` CFG-I4: недостижимый источник истины даёт UNKNOWN, никогда
+правдоподобное значение. «Источник назван, но не снят» — честное «неизвестно», а не «требований по
+облику нет».
+
+**Ворота фазы — детерминированная проверка, после записи профиля:**
+
+```bash
+node .claude/hooks/check-look-trace.cjs .
+```
+
+`0` все строки доехали до `docs/Specification.md` либо отклонены с причиной · `1` потеря доказана,
+потерянные id названы · `2` **проверка НЕ выполнена** (нет профиля, нет спецификации, шаблон не
+тронут, ось «путь» пуста и не объявлена, либо исход не `СНЯТ`) — это НЕ «всё в порядке». До Фазы 1
+код `2` ожидаем: промоушена ещё не было, и здесь проверка отвечает только на вопрос «профиль
+написан и разбирается ли он».
+
+**Куда это идёт.** Фаза 1 промотирует принятые строки `FR-LOOK-nnn` в `docs/Specification.md` — так
+же, как `FR-GROWTH-nnn`. Фаза НЕ утверждает, что интерфейс похож на источник: она ловит ровно один
+класс потерь — облик посмотрели и забыли. Похожесть доказывает визуальное сравнение.
+
+**Checkpoint:**
+```
+═══════════════════════════════════════════════════════════════
+✅ PHASE 0.5: SOURCE PRODUCT PROFILE
+Источник: [название | нет] · облик: [СНЯТ | НЕ ИЗМЕРЕНО (причина) | ИСТОЧНИКА НЕТ]
+                           · путь:  [СНЯТ | НЕ ИЗМЕРЕНО (причина) | ИСТОЧНИКА НЕТ]
+Обязательств по облику: [N]  (облик: [N] · путь: [N])
+⏸️ "ок" — next | "превью облик" — show profile
+═══════════════════════════════════════════════════════════════
+```
+
 ### Phase 1: PLANNING
 
 Read the skill: `.claude/skills/sparc-prd-mini/SKILL.md`
@@ -233,6 +332,10 @@ Product Context: # From Phase 0 (if applicable)
   differentiation: [from Blue Ocean]
   monetization: [from Unit Economics]
 
+Source Look Context: # From Phase 0.5 (ALWAYS present — one of the three outcomes)
+  capture_status: [СНЯТ | НЕ ИЗМЕРЕНО (причина) | ИСТОЧНИКА НЕТ]
+  look_obligations: [rows of docs/source-product-profile.md, FR-LOOK-nnn]
+
 Security Pattern: # If external integrations
   api_keys_input: "UI Settings > Integrations"
   storage: "Encrypted IndexedDB (AES-GCM 256-bit)"
@@ -257,6 +360,18 @@ Write all 11 documents to `docs/`:
 - `docs/C4_Diagrams.md` (if applicable)
 - `docs/ADR.md` (if applicable)
 
+**Промоушен семян — один шаг для двух семейств.** Принятые строки `FR-GROWTH-nnn` (из
+`docs/product-discovery-brief.md`) и `FR-LOOK-nnn` (из `docs/source-product-profile.md`) переносятся
+в `docs/Specification.md` — каждая либо как требование, либо как отклонение С ПРИЧИНОЙ в той же
+строке. Молча уронить нельзя: это ловят `check-growth-trace.cjs` и `check-look-trace.cjs`.
+
+**The handoff manifest is WIDER than the two seeds.** Phase 0 ends the brief with
+`## Манифест передачи` — the enumerated outputs of the REAL run, each with a stable `PD-WORD-nnn`
+id. Phase 1 MUST answer for EVERY one: cite it in a Phase-1 document, or reject it WITH A REASON.
+Silence is forbidden, because an output nobody must answer for is written the same way whether it
+was used or dropped. Checked by `node .claude/hooks/check-handoff-manifest.cjs .` — `2` means THE
+CHECK DID NOT RUN, never "all clear".
+
 Git commit: `docs: SPARC documentation for [project-name]`
 
 **Checkpoint:**
@@ -295,6 +410,7 @@ Created [N] documents in docs/
 
 ```bash
 node .claude/hooks/check-docs-complete.cjs .
+node .claude/hooks/check-external-deps.cjs .
 ```
 
 | Код | Что делать |
@@ -303,6 +419,11 @@ node .claude/hooks/check-docs-complete.cjs .
 | `1` | **НЕ запускайте рой.** Вернитесь в Фазу 1 и допишите названные документы |
 | `2` | проверка не выполнена — почините вызов и повторите; это НЕ «всё в порядке» |
 
+**Инвентарь внешних зависимостей ОБЯЗАН СУЩЕСТВОВАТЬ, и отсутствующий раздел — это НЕ «зависимостей
+нет».** На пустом множестве зелёный вердикт «ни одна внешняя зависимость не UNCONFIRMED и не
+CONTRADICTED» истинен САМ СОБОЙ — вакуумная истина в роли проверки. Продукт, который действительно
+никого не зовёт, пишет это дословно.
+
 Причина, по которой шаг стоит здесь, а не внутри роя: существование файла, его пустота и
 незаполненный шаблон решаются сорока строками кода. Отправлять на этот вопрос рой агентов — значит
 платить вероятностной проверкой за то, что решается детерминированно. Рою остаётся то, ради чего он
@@ -311,6 +432,22 @@ node .claude/hooks/check-docs-complete.cjs .
 Ограничение, которое проверка печатает сама: она доказывает, что документы НАПИСАНЫ, а не что они
 верны. Верность — работа роя.
 
+**Шаги 2.1–2.4 — условные критерии приёмки.** Запускайте только проверки поверхностей продукта;
+отсутствующая поверхность законно даёт `2`.
+
+| Шаг / поверхность | Зачем | Правило | Команда |
+|---|---|---|---|
+| 2.0 Чужой разбор | ГИПОТЕЗА без датированного живого подтверждения не промотируется | `.claude/rules/replicate-pipeline.md` | `node .claude/hooks/check-look-origin.cjs .` |
+| 2.1 Встраиваемый виджет на ЧУЖОЙ странице | три origin-невидимых отказа | `.claude/rules/embeddable-widget.md` | `node .claude/hooks/check-embed-contract.cjs .` |
+| 2.2 Долгая задача (МИНУТЫ) | «нет ответа» ≠ «выполняется»: иначе потерянный оплаченный результат, повтор с нуля и третья копия | `.claude/rules/long-running-job.md` | `node .claude/hooks/check-job-contract.cjs .` |
+| 2.3 Входящий вебхук | событие повторяется и может прийти от кого угодно | `.claude/rules/incoming-webhooks.md` | `node .claude/hooks/check-webhook-contract.cjs .` |
+| 2.4 Платная модель | потраченного не вернуть; несконфигурированный потолок ОБЯЗАН валить запуск, не означать бесконечность | `.claude/rules/model-call-cost.md` | `node .claude/hooks/check-model-cost.cjs .` |
+
+У каждого стража три кода: `0` проверено · `1` дефект ДОКАЗАН и назван · `2` проверка НЕ ВЫПОЛНЕНА — и это НЕ «в порядке»: код 2 никогда не читается как успех, у него в выводе названа причина, и она попадает в отчёт фазы дословно.
+
+Для каждой команды: `0` проверено · `1` дефект ДОКАЗАН и назван · `2` проверка НЕ ВЫПОЛНЕНА — и это
+НЕ «в порядке».
+
 Read the skill: `.claude/skills/requirements-validator/SKILL.md`
 
 **Goal:** Verify all documentation for completeness, testability, and implementation readiness.
@@ -329,13 +466,11 @@ Read the skill: `.claude/skills/requirements-validator/SKILL.md`
 The sixth lens is the only one that looks OUTSIDE the documents. The other five compare our own
 output with our own output, which cannot discover that a service does not do what we assumed.
 
-**Positive file receipt (required).** Before dispatch, allocate one `RUN_ID` and give every
-validation lens a unique `WORK_UNIT_ID` and absolute `TRACE_PATH`. Each validator must write a
-substantive report fragment ending in `Status: completed` or `Status: failed` to `TRACE_PATH` before
-its one-line pointer. Before AGGREGATE, verify every path is a regular non-symlink file,
-non-whitespace, post-launch, and terminal. Narrative output or silence is not a receipt. Name
-missing, stale, partial, unreadable, duplicate, failed, dead-PID, or probe-error lenses and refuse
-aggregation/completion unless every required receipt is valid and completed. See
+**Positive file receipt (required).** Assign each validation lens a unique `WORK_UNIT_ID` and unique
+absolute `TRACE_PATH`. Its validator MUST write a substantive fragment ending in `Status: completed`
+or `Status: failed` to `TRACE_PATH` before its one-line pointer. Before AGGREGATE, verify a regular,
+non-symlink, substantive, post-launch file with a terminal status. Narrative/chat/silence is never a
+receipt; any invalid receipt MUST block aggregation/completion. Full rule:
 `.claude/rules/swarm-file-evidence.md`.
 
 **Process (iterative, max 3 iterations):**
@@ -481,12 +616,9 @@ Read the skill: `.claude/skills/cc-toolkit-generator-enhanced/SKILL.md`
 **IMPORTANT (Claude Code adaptation, post v1.4):**
 - Scan `docs/` directory for SPARC documents (NOT `/mnt/user-data/uploads/`)
 - Generate files IN-PLACE into the project (NOT into output directory)
-- **Pre-shipped by `npx p-replicator init` — do NOT overwrite or regenerate:**
-  - All 10 skills in `.claude/skills/`
-  - All 11 commands: `/replicate`, `/harvest`, `/start`, `/plan`, `/feature`, `/go`, `/run`, `/next`, `/myinsights`, `/docs`, `/deploy`
-  - All 9 rules: `cost-of-detection-ladder`, `replicate-pipeline`, `skill-interface-protocol`, `git-workflow`, `insights-capture`, `feature-lifecycle`, `docker-ports`, `swarm-file-evidence`, `honest-configuration`
-  - All 4 pipeline agents: `replicate-coordinator`, `product-discoverer`, `doc-validator`, `harvest-coordinator`
-  - `.claude/settings.json` + cross-platform Node hook scripts in `.claude/hooks/`
+- The toolkit pre-shipped by `npx p-replicator init` is enumerated in
+  `.claude/rules/replicate-pipeline.md`; do NOT overwrite or regenerate any listed skill, command,
+  rule, agent, setting, or hook.
 - Phase 3 generates ONLY project-specific artifacts derived from SPARC docs (see below).
 
 **Generate these project-specific files:**
@@ -568,22 +700,9 @@ git commit -m "chore: initial project setup from SPARC documentation"
 ═══════════════════════════════════════════════════════════════
 ✅ REPLICATE COMPLETE: [project-name]
 
-📁 Project structure:
-├── CLAUDE.md                     # Project context
-├── DEVELOPMENT_GUIDE.md          # Dev lifecycle guide
-├── README.md                     # Quick start
-├── docs/                         # [N] SPARC documents
-│   ├── validation-report.md      # Validation results
-│   ├── test-scenarios.md         # BDD scenarios
-│   └── features/                 # For future features
-├── .claude/
-│   ├── commands/                 # /start, /feature, /plan, /go, /run, /deploy, /myinsights
-│   ├── agents/                   # planner, code-reviewer, architect
-│   ├── skills/                   # 8 shared + project-specific skills
-│   ├── rules/                    # git-workflow, security, coding-style, ...
-│   └── settings.json             # Hooks (insights auto-commit)
-├── docker-compose.yml            # Scaffold
-└── Dockerfile                    # Scaffold
+📁 Project structure: CLAUDE.md · DEVELOPMENT_GUIDE.md · README.md · docs/ ([N] SPARC документов,
+validation-report.md, test-scenarios.md, features/) · .claude/ (commands, agents, skills, rules,
+settings.json) · docker-compose.yml · Dockerfile
 
 🚀 Next steps:
 1. Run /start to bootstrap the project
@@ -635,6 +754,7 @@ PRINCIPLE: User enters keys via UI → stored encrypted in browser → NEVER sen
 | `ок` | Next phase |
 | `превью [filename]` | View generated file |
 | `превью discovery` | Show Product Discovery Brief |
+| `превью облик` | Show Source Product Profile (Phase 0.5) |
 | `превью validation` | Show Validation Report |
 | `превью toolkit` | Show toolkit structure |
 
@@ -642,6 +762,9 @@ PRINCIPLE: User enters keys via UI → stored encrypted in browser → NEVER sen
 
 ### ALWAYS
 - Read skill SKILL.md before executing its logic
+- Run Phase 0.5 in EVERY run, including `--from-docs`, and write `docs/source-product-profile.md` in
+  all three outcomes — an absent profile and one saying «источника нет» look identical to the next
+  reader and mean different things
 - Checkpoint after each phase
 - Pass Architecture Constraints to sparc-prd-mini
 - Write docs to `docs/` directory (not `/output/`)
@@ -657,4 +780,6 @@ PRINCIPLE: User enters keys via UI → stored encrypted in browser → NEVER sen
 ### CONDITIONAL
 - If external APIs → include security-patterns/ skill + secrets-management.md rule
 - If new product → start with Phase 0 (Product Discovery)
+- If the project replicates an existing product → Phase 0.5's captured look SUPERSEDES the industry
+  palette of `025-cjm-prototype.md`, which is a LABELLED fallback for the other two outcomes only
 - If B2B/Enterprise → strengthen security patterns in validation