verify-paranoid

原文涵盖的主题

• verify-paranoid workflow (v3)
• Overview
• Capability refs
• Gate ref
• Routing rules (sister CLAUDE.md "gstack 治理关卡")
• How to invoke
• References

1-phase sub-workflow mapping CLAUDE.md "gstack 治理关卡 🔒 关键模块 PR 前强制 — /review" onto harnessed runtime (Phase v3.0-3.4 W0.12 — D-04 Stage ④ Verify 7 sub + D-12 gstack 治理关卡 + Pattern A sub-workflow ship)。 | phase | id | upstream | model | capability | gate | | ----- | -- | -------- | ----- | ---------- | ---- | | 1 | 01-review | gstack | opus | {{ capabilities.gstack-review.cmd }} | judgments.stage-routing.verify-paranoid-critical.fires | Per-phase config loads from workflows/verify/paranoid/workflow.yaml; engine 4-level gate resolver evaluates phase.iscriticalmodule == true via expr-eval — true 则 invoke gstack /review, false 则 skip (chainisolation 3 铁律 R20.16 sister verify-work v2 phase 04)。 Sister workflows/capabilities.yaml entries: gstack-review — Bucket 3 治理关卡 (impl: gstack, cmd: /review, fireswhen: phase.iscriticalmodule == true) Sister workflows/judgments/stage-routing.yaml: verify-paranoid-critical.fires — phase.stage == 'verify' and phase.iscriticalmodule == true (默认 critical fire only; 普通 PR 应跳过 — gstack-review 是 Paranoid Staff Engineer 重武器) ✅ 触发: 关键模块 PR 前 (auth / payment / data migration / core algorithm 等) ❌ 跳过: 常规 PR / docs / config / 非核心 module !harnessed checkpoint int

这里只展示节选，请以完整原文和当前要求为准。