genesis-evalslisted

# genesis-evals: maintainer-side eval runner Run the genesis self-eval suite. Steers the parent LLM session to orchestrate cold sub-agent spawns, capture responses, score deterministically, and report convergence. ## Why this lives outside `.apm/` Genesis ships to USERS via npx / `apm install`. Eval scenarios LOOK LIKE real user requests (that is the point). Colocating them under `skills/genesis/evals/` would risk DISPATCH CONTAMINATION (an over-eager harness loader pulling scenario prompts into the active context) and PAYLOAD BLOAT for users who never run evals. We also keep this OUTSIDE `.apm/` because APM treats `.apm/` as the publishable source root: its local-content scanner picks up anything under `.apm/skills/` regardless of dev-marker, so `apm pack --format plugin` would leak this maintainer-only skill into the shipped artifact. Living under `dev/skills/` keeps it scanner-invisible while still letting `apm install --dev` deploy it via the local-path devDependency in the root `apm.yml`. This is the inverse of PHANTOM DEPENDENCY (referenced-but-not-bundled): BUNDLE LEAKAGE (bundled-but-not-consumed-at-runtime). See `skills/genesis/assets/composition-substrate.md` "Anti-patterns flagged at this step". ## When to activate - Validating a genesis PR before merge - Any change to a file under `skills/genesis/` (catalogue or SKILL.md) - Operator says "run evals", "regenerate eval matrix", "score on Opus" - Adding a new scenario (run validate first) ## Hard rules - The