Verify completed phase deliverables against plan must-haves (truths, artifacts, key links) and threat mitigations, producing a structured verification report. @.opencode/references/hm-coordination-contracts.md @.opencode/references/hm-dual-signal-completion.md Outputs generated by this workflow are consumed by: 1. **hm-gate**: Evaluates the `VERIFICATION.md` file during the evidence truth gate check. 2. **Milestone transitions**: Required before archiving a completed milestone. **CRITICAL: Objective verification.** Verification must rely on concrete runtime evidence. Do not claim verification passes based on doc summaries or code inspection alone where live execution is possible (mock detection rules apply). Load phase details. Read `PLAN.md` and `SUMMARY.md` from the phase directory. Check for existing verification results. Scan the filesystem for all artifacts defined in the plan's frontmatter: - Check that each file path exists. - Verify files are non-empty and have non-zero size. - Log LOC and file size metrics. Evaluate each truth statement in the plan frontmatter: - Execute the specific tests or commands that demonstrate the behavior. - Capture the stdout, test logs, or console output. - Record the evidence level (L1 runtime output, L2 test trace, etc.). Check defined relationships and pattern matching: - Use grep or AST queries to confirm links (e.g. function call, event subscriber registration). - Log the pattern match coordinates. Check each threat mitigation defined in the plan's threat register. Validate that the mitigation component is implemented and covered by automated tests. Execute the full automated test suite to gather a final validation log. Capture the test pass rate and total runtime. Generate `${phase_dir}/${padded_phase}-VERIFICATION.md` using the standard `hm-verification` template: - Mark PASS/FAIL for each must-have item. - Attach specific run/test evidence logs. - Document overall Pass/Fail verdict. Stage and commit the generated `VERIFICATION.md` file atomically to git. Record verification status in `.planning/STATE.md` and commit. - Every plan artifact, truth, and link verified. - Concrete evidence logs attached to each verdict. - STRIDE threat mitigations validated. - `VERIFICATION.md` written and committed.