Update to OpsTruth

{
  "description": "Use this when a user asks whether a public GitHub repository has visible CI, deployment, packaging or handoff evidence for a release. It never deploys or publishes; conclude only with Ready for live validation, Insufficient evidence or Not ready.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 485
    }
  ],
  "name": "verify-release-readiness",
  "skill_md_contents": "---\nname: verify-release-readiness\ndescription: Use this when a user asks whether a public GitHub repository has visible CI, deployment, packaging or handoff evidence for a release. It never deploys or publishes; conclude only with Ready for live validation, Insufficient evidence or Not ready.\n---\n\n# Verify Release Readiness\n\nRequire a public GitHub repository URL or `owner/name`.\n\n1. Call `opstruth_check_github_handoff` for current public GitHub Actions, check-run, commit-status, branch-protection, contribution and handoff evidence.\n2. Call `opstruth_check_deployment` for static deployment configuration and platform indicators.\n3. Call `opstruth_review_migrations` when database migrations are present.\n4. Call `opstruth_review_api_contracts` when release safety depends on APIs or schemas.\n5. Call `opstruth_probe_deployment` only when the user supplies the public HTTPS deployment URL and the relevant health paths.\n6. Call `opstruth_prepare_sandbox_verification` when fresh build, test or typecheck evidence is still required. Present its exact repository commit and commands for approval in a separately connected runner.\n7. Summarize blockers, warnings and missing proof. Never convert a static configuration match, historical CI run or health response into broader application correctness.\n8. Stop before execution, release, deployment, publication, migration or provider mutation in the public plugin.\n\nConclude with one of: ready for live validation, not ready, or insufficient evidence.\n"
}