verify-second-opinion

原文涵盖的主题

• verify-second-opinion workflow (v3)
• Overview
• Capability refs
• Gate ref
• Routing rules
• How to invoke
• References

1-phase sub-workflow — 编排契约改动时的跨模型第二意见 (Phase 54 T2)。 | phase | id | upstream | model | capability | gate | | ----- | -- | -------- | ----- | ---------- | ---- | | 1 | 01-second-opinion | gstack | sonnet | {{ capabilities.codex.cmd }} | judgments.stage-routing.verify-second-opinion-orchestration.fires | 判据不是交给模型的判断题。harnessed facts 把 git diff --name-only 与 ORCHESTRATION SURFACE (judgments / capabilities / 事实 schema / resolver / exprBuilder / ledger / disciplines / 任一 workflows SKILL.md) 求交集,机械得出 requiressecondopinion。 基准是上一个 release tag,不是 merge-base origin/main —— 后者在 commit-即-push-main 的纪律下塌缩成 HEAD,只看得见未提交改动,会漏掉多-commit milestone 的早期 commit。 算不出来 (无 tag / 无 git / diff 失败) 时取 false,并在每轮 断点打出 SECOND-OPINION: 判据不可用( )。不乱 fire,且不静默。 Sister workflows/capabilities.yaml entries: codex — 第二意见 / cross-AI peer review via codex (impl: gstack, cmd: /codex) Sister workflows/judgments/stage-routing.yaml: verify-second-opinion-orchestration.fires — phase.stage == 'verify' and requiressecondopinion == true ✅ 触发: 本次改动触及编排契约本身 (judgments / capabilities.yaml / phaseFactContext / facts.ts / judgmentResolver / exprBuilder / ledger.ts / disciplines / 任一 SKILL.md) ❌ 跳过: 纯 installer / 文档 / 测试 / 依赖 bump

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