verify-validate-phaselisted

# verify-validate-phase workflow (v3) ## Overview 1-phase sub-workflow auditing requirement→test coverage gaps (v13.0 P43 upstream re-sync — D-04 Stage ④ Verify conditional sub + GSD validate-phase wire)。回溯审计 phase 完成后的 requirement→test 覆盖缺口,为未覆盖 requirement 生成测试 (gsd-nyquist-auditor agent), 补 TDD 前向写测试之外的后向查漏。 | phase | id | upstream | model | capability | gate | | ----- | -- | -------- | ----- | ---------- | ---- | | 1 | `01-validate-phase` | gsd | sonnet | `{{ capabilities.gsd-validate-phase.cmd }}` | `judgments.stage-routing.verify-validate-phase-coverage.fires` | Per-phase config loads from `workflows/verify/validate-phase/workflow.yaml`; engine 4-level gate resolver evaluates `phase.requires_coverage_audit == true` via expr-eval — true 则 invoke GSD `/gsd-validate-phase` (Nyquist 覆盖审计 → VALIDATION.md), false 则 skip。 ## Capability refs Sister `workflows/capabilities.yaml` entries: - `gsd-validate-phase` — Bucket 2 special-purpose (impl: gsd, cmd: /gsd-validate-phase, fires_when: requires_coverage_audit) ## Gate ref Sister `workflows/judgments/stage-routing.yaml`: - `verify-validate-phase-coverage.fires` — `phase.stage == 'verify' and phase.requires_coverage_audit == true` ## How to invoke !`harnessed checkpoint intent verify-validate-phase` > 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-inten