vibepro-gate-evidencelisted

# VibePro Gate Evidence Playbook ## Purpose Distilled operating knowledge for closing VibePro gates efficiently. `pr prepare` tells you *which* gates block; this Skill tells you *how* to produce evidence that actually resolves them, in the right order, without stale-evidence rework. ## When to Use Use this Skill when recording `vibepro verify record` / `vibepro review record` evidence, writing Architecture or Spec artifacts through the CLI, or when `pr prepare` / `gate check` reports `needs_verification`, `needs_review`, or specific unresolved gate ids. Also use it before deciding the commit/evidence/review order for any VibePro-managed change. ## Required Workflow 1. Finalize the entire tree (see Commit Ordering Rule below). 2. Record verification evidence with structured observations and strong artifacts. 3. Run the Agent Review lifecycle once, in order, with honest inspection inputs. 4. Run the adjudication gates (evidence + judgment DAG) with an independent fresh-context subagent. 5. `pr prepare --summary-json`, resolve remaining gate ids using the troubleshooting patterns, then `pr create`. ## Commit Ordering Rule (most important) Verification and review records are content-surface-bound by default. A later commit only makes them stale when it changes a recorded target or inspected file. Configured high-risk review roles remain strict-HEAD-bound; a CLI override requires both `--strict-head-binding` and `--strict-head-reason`. 1. Finalize the intended verificatio