feat(prompts/templates): first-class verification states; forbid bare 'skipped' when checks ran

[bradtaylorsf]

Problem

Across real runs, verification is frequently recorded as a bare "skipped" even though tests/lint/typecheck/build ran and passed — conflating "automated checks passed, runtime not exercised" with a true skip. This makes the verification signal worthless and hides genuinely unverified deployed paths.

Proposed change

Bake explicit verification states into the verify + learn prompts and the distribution seeded templates, so every new repo gets them by default (not only after a per-project review --apply):

• automated_passed (with commands + results), runtime_verified, or skipped(reason, residual_risk).
• Forbid "skipped" when automated checks ran; require the exact commands and results.

Files

src/lib/prompts.ts, templates/agents/{reviewer,implementer}.md, templates/skills/{alpha-loop-runner,testing-patterns}/SKILL.md.