verify

name	verify
description	Three-stage verification: V1 unit → V2 integration → V3 E2E + evidence package
argument-hint	<feature-id e.g. F001>

Verify — Three-Stage Verification

Parameter: $ARGUMENTS — feature ID (e.g. F001)

V1: Unit/Component Tests

1. Run all V1 tests for this feature
2. Check coverage ≥ 80%
3. If any fail → STOP, fix first
4. Record results to .harness/evidence/$ARGUMENTS/v1-result.md

V2: Integration Tests

1. Run all V2 tests for this feature
2. Verify cross-module data flow correctness
3. Verify API contracts match spec
4. If any fail → STOP, fix first
5. Record results to .harness/evidence/$ARGUMENTS/v2-result.md

V3: End-to-End Tests

1. Run all V3 tests
2. Execute complete user paths defined in spec
3. Capture screenshots at key steps (if applicable)
4. Compare with baseline screenshots (if available)
5. Record results to .harness/evidence/$ARGUMENTS/v3-result.md

Evidence Package

Create .harness/evidence/$ARGUMENTS/verdict.md:

# Verification Verdict — $ARGUMENTS

## Summary
- Feature: [name]
- Date: [timestamp]
- Result: PASS / FAIL

## Acceptance Criteria Status
| AC | Description | V1 | V2 | V3 | Status |
|----|-------------|----|----|-----|--------|
| AC-1 | ... | PASS | PASS | PASS | ✅ |
| AC-2 | ... | PASS | FAIL | - | ❌ |

## Invariant Status
| INV | Description | Status |
|-----|-------------|--------|
| INV-1 | ... | ✅ |

## Coverage
- V1 coverage: XX%
- Lines: X/Y

## Issues Found
- [list any issues discovered during verification]

Pitfalls Collection

After verification, review the entire feature development for lessons learned:

1. Read .harness/pitfalls.md (if exists)
2. Review all issues found during V1/V2/V3 — any surprising failures or non-obvious fixes should become pitfalls
3. Review .harness/evidence/$ARGUMENTS/verdict.md — any AC that required multiple attempts
4. Append new pitfalls to .harness/pitfalls.md:
   • Format: - [module/area]: concise pitfall description
   • One fact per line, no fluff
   • Do NOT duplicate existing entries
   • Only record non-obvious pitfalls (things you can't deduce from reading the code)

Completion

• Update .harness/tasks.md: set feature status to verified
• Update .harness/progress.md with verification results
• Notify user for final acceptance