evaluate-landing-pagelisted

# Landing Page Eval — Orchestrator <!-- BUDGET_EXCEPTION: Eval skills carry artifact-schema-as-contract (8 body sections + 8-col results row + cross-stack consumer contract) that is load-bearing and cannot move to references/. Cycle ledger discipline requires the schema be visible in the SKILL.md body. ~300 tokens over the standard cap is the legitimate cost. --> *Evaluation skill. Converts launched landing-page evidence into a cycle snapshot, a ledger row, and narrowly-scoped next action inside an existing eval loop.* **Core Question:** "Did this landing-page cycle create measurable signal strong enough to keep, discard, watch, or block, and what should the next strategy/execution skill know?" > Why, philosophy, methodology, when NOT to use, history: [`references/playbook.md`](references/playbook.md) [PLAYBOOK]. ## Critical Gates 1. **Existing eval loop required.** If `.forsvn/loops/[slug]/program.md` + `context.md` absent → `NEEDS_CONTEXT`, recommend `/run-eval-loop`. This skill does not create loops. 2. **Measurement evidence required.** Not a generic heuristic audit. Require ≥1 metric source, measurement window, and current value for the loop's primary metric. 3. **One primary metric decides the ledger row.** Secondary metrics and qualitative evidence explain diagnosis; they do not override the primary metric unless `program.md` defines an explicit guardrail failure. 4. **No fabricated analytics.** Unknown values stay unknown. Manual notes only when labeled operator