chore: import upstream snapshot with attribution

docs/management/runs/add-tags.mdx

@@ -0,0 +1,4 @@
+---
+title: "Add tags to a run"
+openapi: "v3-openapi POST /api/v1/runs/{runId}/tags"
+---

docs/management/runs/cancel.mdx

@@ -0,0 +1,4 @@
+---
+title: "Cancel run"
+openapi: "v3-openapi POST /api/v2/runs/{runId}/cancel"
+---

docs/management/runs/list.mdx

@@ -0,0 +1,4 @@
+---
+title: "List runs"
+openapi: "v3-openapi GET /api/v1/runs"
+---

docs/management/runs/replay.mdx

@@ -0,0 +1,4 @@
+---
+title: "Replay run"
+openapi: "v3-openapi POST /api/v1/runs/{runId}/replay"
+---

docs/management/runs/reschedule.mdx

@@ -0,0 +1,4 @@
+---
+title: "Reschedule run"
+openapi: "v3-openapi POST /api/v1/runs/{runId}/reschedule"
+---

docs/management/runs/retrieve-events.mdx

@@ -0,0 +1,4 @@
+---
+title: "Retrieve run events"
+openapi: "v3-openapi GET /api/v1/runs/{runId}/events"
+---

docs/management/runs/retrieve-result.mdx

@@ -0,0 +1,4 @@
+---
+title: "Retrieve run result"
+openapi: "v3-openapi GET /api/v1/runs/{runId}/result"
+---

docs/management/runs/retrieve-trace.mdx

@@ -0,0 +1,8 @@
+---
+title: "Retrieve run trace"
+openapi: "v3-openapi GET /api/v1/runs/{runId}/trace"
+---
+
+Returns the OpenTelemetry trace subtree for the run you request. The response `trace.rootSpan` is that run's span — not necessarily the trace-wide root — with its descendant spans nested under `children`.
+
+For a child or nested run inside a large trace, this endpoint scopes the tree to that run so you still get a useful subtree even when the full trace has more spans than the platform can return in one response.

docs/management/runs/retrieve.mdx

@@ -0,0 +1,4 @@
+---
+title: "Retrieve run"
+openapi: "v3-openapi GET /api/v3/runs/{runId}"
+---

docs/management/runs/update-metadata.mdx

@@ -0,0 +1,4 @@
+---
+title: "Update metadata"
+openapi: "v3-openapi PUT /api/v1/runs/{runId}/metadata"
+---