Commit Graph

5 Commits

Author SHA1 Message Date
Дмитрий cc77a5817e docs(phase8): owner deployment runbook for M7 zoo dissolution + activation 2026-06-09 13:03:56 +03:00
Дмитрий 487a6f1db9 docs(router-mentor): A1 judge gate2 activation note (implementation-specific) 2026-06-09 08:55:33 +03:00
Дмитрий 681c2b8abc docs(router-mentor): activation runbook A1 A6 A7 2026-06-09 07:50:42 +03:00
Дмитрий cebd6bcebb docs(router-gate-v4): Stream H Task 1 fix — correct module references in recovery-procedures.md (code-quality review)
Code-quality reviewer flagged 2 IMPORTANT factual inaccuracies in
recovery-procedures.md (commit 3ce73a68):

1. Section 6 RECOMMENDED code example imported resolvePathNormalize from
   the wrong module path (tools/shell-content-rules.mjs). Actual exporter
   is tools/enforce-router-gate.mjs (verified via Grep at line 174).
   shell-content-rules.mjs only exports defaultPathNormalize. A future
   reader copying the RECOMMENDED pattern would get an import error.
   Also corrected the call signature: resolvePathNormalize() takes no
   arguments and is async — returns the normalize function directly.

2. Section 4 (Stale-process) cited tools/enforce-bash-content-gate.mjs —
   no such file exists in tools/ (verified via Glob). Correct hook
   filenames are enforce-router-gate.mjs (Bash) and
   enforce-powershell-gate.mjs (PowerShell).

Fix: replace both module references with the verified correct filenames
(Grep'd against tools/ exports + Glob'd file existence). Also includes
the lefthook MD032 blank-lines-around-lists auto-format diff carried
over from the previous commit's post-commit hook.

Surgical edit — no new content, no restructuring.
2026-05-30 10:13:16 +03:00
Дмитрий 3ce73a68ff docs(router-gate-v4): Stream H Task 1 — recovery-procedures.md (3 levels + stale-process + 7 fabrications + test methodology + smoke methodology)
Adds first-time recovery runbook with:
- 3 self-recovery levels (Level 1 ≤5min sentinel reset, Level 2 ≤15min VS Code
  restart, Level 3 destructive workspace rebuild)
- Stale-process / hook reload trap (Smoke 5 chistaa-session hypothesis +
  refutation method); key takeaway: live restart-test is the only way to
  confirm a hook-modifying fix landed
- Self-fabrication patterns — 7 cases enumerated from Smokes 3/4/5/7 with
  pattern signature, detection signal, mitigation for each
- Test methodology lesson — Smoke 5 root cause showed unit tests with inline
  mocks can give false-green if they bypass the live resolver function; debug
  scripts have the same trap
- Smoke methodology — statusline-setup system prompt overrides user tasks
  (Smoke 9 Run 1); use semgrep-scanner for echo-probes, statusline-setup OK
  for gate-inheritance smokes

Docs-only change; verified via docs-only short-circuit in enforce-verify-
before-push (§5 п.13 CLAUDE.md).

Stream H Task 1 of 11. Plan: docs/superpowers/plans/2026-05-30-router-gate-v4-stream-H.md
2026-05-30 09:58:38 +03:00