Porting Validate

---
name: porting-validate
description: Run the validation checklist before the milestone's final commit. Checks runtime verification, visual correctness, reference artifact comparison, Metal validation, memory leaks, skill-driven code review, and data flow verification. Can also be run mid-milestone.
disable-model-invocation: true
---

You are entering Phase 3: Validate for the current milestone. The milestone's work is functionally complete. Mid-milestone commits for stable checkpoints are fine, but this full validation pass should happen before closing out the milestone.

## Reload Skills

Validation often runs in a fresh session after the execute phase. Skills loaded during execution are no longer in context. **You MUST reload the skills you need before proceeding:**

1. **Always reload** `porting-methodology` (for anti-patterns checklist and debugging escalation).
2. **For rendering milestones**, reload `using-gpucapture` and `using-gpudebug` — you will need these for GPU frame capture and ground truth comparison. Do NOT attempt GPU capture workflows from memory.
3. **Reload domain skills** for this milestone. Read the goal document's milestone plan to find which skills are associated with the current milestone. Also check porting-memory.md for any additional context. You need these for the skill-driven code review (checklist item 7).
4. **If visual bugs are found**, reload `debugging-rendering-issues` for structured diagnostic workflows.

## Validation Checklist

Work through each item and report findings:

### 1. Runtime Verification

**The app must run.** From M1 onward, do not declare a milestone complete based on code review alone — verify at runtime.