verify-eval-reviewlisted

# verify-eval-review workflow (v3) ## Overview 1-phase sub-workflow auditing AI phase eval coverage (v13.0 P42 upstream re-sync — D-04 Stage ④ Verify conditional sub + GSD eval-review wire)。Pairs with the plan-side `gsd-ai-integration-phase` (AI-SPEC.md eval strategy): verify 侧回查实现是否真覆盖规划的 eval 维度,产出 EVAL-REVIEW.md (逐维度 COVERED/PARTIAL/MISSING)。 | phase | id | upstream | model | capability | gate | | ----- | -- | -------- | ----- | ---------- | ---- | | 1 | `01-eval-review` | gsd | sonnet | `{{ capabilities.gsd-eval-review.cmd }}` | `judgments.stage-routing.verify-eval-review-aiphase.fires` | Per-phase config loads from `workflows/verify/eval-review/workflow.yaml`; engine 4-level gate resolver evaluates `phase.has_ai_phase == true` via expr-eval — true 则 invoke GSD `/gsd-eval-review` (eval 覆盖审计 → EVAL-REVIEW.md), false 则 skip。 ## Capability refs Sister `workflows/capabilities.yaml` entries: - `gsd-eval-review` — Bucket 2 special-purpose (impl: gsd, cmd: /gsd-eval-review, fires_when: has_ai_phase) ## Gate ref Sister `workflows/judgments/stage-routing.yaml`: - `verify-eval-review-aiphase.fires` — `phase.stage == 'verify' and phase.has_ai_phase == true` ## How to invoke !`harnessed checkpoint intent verify-eval-review` > The banner above (when present) means this invocation is REGISTERED with the engine (an intent marker) — not yet compliant: the steps below (prompt → spawn → checkpoint complete) resolve it, and a per-turn `<workflow-intent>` reminder persists until t