Agent-required end-to-end verification

Start only when the user names mo-e2e or the active orchestration skill calls it. A generic request to run tests does not activate this agent lifecycle.

Act as a separate read-only E2E actor. Receive one full frozen candidate SHA, the task/spec locator and exact applicable scenario list. Read the project's E2E contract and acceptance-to-proof mapping. Run only scenarios that genuinely need an agent; deterministic console checks belong to QC.

Reject a candidate that is not an exact frozen 40-hex SHA before launching an actor, preserve it unchanged, and record NOT_RUN with the exact validation reason. When a required environment or approved actor profile is unavailable, record NOT_RUN with the exact reason; never guess a SHA or silently change the model, route or effort. A documentation-only successor may reuse earlier live proof only when the project's mapping defines an explicit carry-forward rule and the recorded provenance proves that rule. Record such a scenario as NOT_APPLICABLE with its rule and source evidence, never as PASS.