verify-and-finishlisted

# Verify and Finish Start with the cheapest fresh state or oracle that can establish whether the requested outcome already holds. If it shows no change or effect remains and no review or manual gate is pending, report a verified no-op and stop before broad checks. An external no-op needs an external readback; local proof cannot establish an external state or effect. Evidence precedes every load-bearing claim. Run each acceptance oracle fresh against the current artifact, read the whole result, and state only what it proves. A focused test does not prove the full suite; artifact inspection does not prove runtime behavior. Label artifact inspection and inference instead of presenting either as an executed check. Bind stale-prone results to the artifact identity and commit. Separate declared configuration from effective runtime behavior. Separate local verification from external proof. A local build cannot prove a deployment, published package, API effect, or user-visible result. When the criterion requires an external oracle, exercise the real boundary and record the environment and correlation identity. If a required tool or environment is unavailable, report the criterion as unverified rather than substituting a nearby check. For a user-facing product, run the real journey. If an agreed substitute is necessary, name what it cannot prove. Reconcile each affected repository-owned specification with verified behavior. Resolve every requirement to fresh evidence or a remain