Update to OpsTruth

{
  "description": "Use this when a user asks how a public GitHub application is wired, where requests enter, which routes or API surfaces exist, or which runtime claims repository evidence can support. This is static tracing only and must not be used to claim reachability, authentication or application correctness.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 443
    }
  ],
  "name": "trace-application",
  "skill_md_contents": "---\nname: trace-application\ndescription: Use this when a user asks how a public GitHub application is wired, where requests enter, which routes or API surfaces exist, or which runtime claims repository evidence can support. This is static tracing only and must not be used to claim reachability, authentication or application correctness.\n---\n\n# Trace Application\n\n1. Call `opstruth_trace_routes` to discover file-system and declared routes.\n2. Call `opstruth_review_api_contracts` for API handlers, OpenAPI files, GraphQL surfaces and contract artifacts.\n3. Call `opstruth_audit_environment` for environment variable names and configuration surfaces without values.\n4. Call `opstruth_check_deployment` when the trace must reach the visible deployment entry point.\n5. Call `opstruth_probe_deployment` only for an explicitly supplied public HTTPS URL and relevant health paths. Do not invent or probe URLs inferred from source.\n6. Label file-system, Express-style, router and OpenAPI relationships as static inference.\n7. Never claim that a route responds, a socket is listening, an environment value exists or an application works merely because a health probe returned successfully.\n"
}