docs(skill): принцип «мастер решает», готовые boilerplate-промпты, ревизия

- Зачем:
  - ретро прогона 2026-07-12 (задача 20, clickstream-demo): контекст
    оркестратора съедали инлайн-диагнозы, переписывание boilerplate и
    кириллица в обменных файлах.
- Что:
  - SKILL.md: принцип «мастер решает — субагенты выясняют» со стоп-краном
    «сам — максимум один заход», обменные файлы на английском, сквозная
    проверка до ревьюеров, будильник одной строкой.
  - references/prompts/: готовые английские boilerplate-файлы (мандат
    ревью, триаж, перепроверка) — подшиваются cat'ом, контекст мастера
    не проходят; prompt-templates перестроен под сборку.
  - codex-exec: модель gpt-5.6-sol, лестница эффорта, ловушка «&»;
    sandbox-справочник переименован в codex-sandbox-apparmor.md;
    lessons дистиллирован, добавлена запись прогона 2026-07-12.
  - закрыты 14 находок слепого Fable-ревью скилла (согласованность,
    единый источник $SCRATCH, скелет ревью постановки).
- Проверка:
  - все внутренние ссылки резолвятся; слепое ревью: APPROVED_WITH_MINORS,
    восстановление структуры подтверждено без потерь.

agents/.agents/skills/claude-subagent-playbook/references/prompts/recheck-header.md

@@ -0,0 +1,13 @@
+# Narrow re-check: do the fixes close your findings?
+
+The implementer has processed the findings of your review. Check ONLY your
+own findings — no full second pass. Mandate unchanged: modify nothing;
+reading and running tests are allowed.
+
+Answer one line per your finding: CLOSED / NOT_CLOSED (why) /
+REJECTION_VALID / REJECTION_INVALID (why). If you spot a NEW defect while
+re-checking, report it in the same index format — narrowness limits scope,
+not honesty. Final line: RECHECK: ALL_CLOSED | ISSUES_REMAIN
+
+The implementer's report path, test command and expected counters are
+appended below.

agents/.agents/skills/claude-subagent-playbook/references/prompts/review-boilerplate.md

@@ -0,0 +1,17 @@
+## Mandate (strict)
+
+- Do NOT modify sources or environment. No edits — findings only.
+- Running tests, verifying hypotheses, reading docs and primary sources —
+  allowed and encouraged; safe empirical checks in temp dirs outside the
+  repo make a verdict much firmer than reading alone.
+- No `git add` / `git commit` / `git checkout`.
+- Output only the findings index and the VERDICT line — no code retelling,
+  no narrative. Where to put it: your call wrapper says, or it is your
+  `-o` report if you were invoked via stdin.
+
+## Findings file format — index only
+
+SEVERITY(BLOCKER|MAJOR|MINOR|NIT) | file:line (or spec/task-file section) | one-phrase essence | how to verify/reproduce
+
+Confirmations of correctness — one line per item, no elaboration.
+Final line: VERDICT: APPROVED | APPROVED_WITH_MINORS | CHANGES_REQUIRED

agents/.agents/skills/claude-subagent-playbook/references/prompts/triage-header.md

@@ -0,0 +1,18 @@
+# Triage of findings from independent blind reviews of your implementation
+
+Below are the findings of the blind reviews, **verbatim**. Close what is
+listed, change nothing else. For each finding, either:
+
+- a TDD fix — first a test reproducing the finding, then the fix; or
+- a reasoned rejection via contract/spec and test — a bare "not important"
+  is not accepted.
+
+No commits. Record rejection arguments in the task file so a fresh thread
+can continue without this thread's context.
+
+Final report: one line per finding — fixed (how) / rejected (argument +
+where recorded); test command, run counters, list of changed files.
+
+Orchestrator notes, if present below, carry task-level decisions (out of
+scope / risk accepted) and verified facts you don't have — they are not
+findings to fix.