verifylisted

# Verification gate Prove that the requested scope, current evidence, implementation, tests, and governing artifacts agree. `verify` owns `branch-ready`; `pr` owns `pr-body-ready` and `pr-open-ready`. ## Purpose Perform either a bounded evidence check or a final readiness assessment without taking ownership from authoring, review, workflow, or PR stages. Final verification validates the final change pack after `explain-change` and before PR. Final verification is scoped evidence and must not own artifact settlement, milestone state, or routing. For planned work, use `change.yaml` to assess current state and treat the plan and upstream artifacts as read-only. ## When to use Use this skill for an explicit validation surface, a direct branch-readiness assessment, or governed final verification after implementation, review closeout, triggered CI maintenance, and durable change rationale are complete. ## When not to use Do not use it to replace code-review, settle upstream artifacts, repair implementation, prepare or open a PR, or claim hosted CI that was not observed. ## Workflow role `verify` evaluates evidence and records only verify-owned results. The `workflow` skill owns lifecycle progression, and `pr` owns PR preparation and opening. A successful workflow-managed verification hands off to `pr`; it never invokes `pr` itself. Run `ci-maintenance` first when hosted workflow automation, validation automation, or related platform configuration must change. ## Project