List the inbox reports a run's findings linked to

v1.0.0

Best-effort reverse of the report -> signals link. For each finding the run emitted, resolve the inbox SignalReport (if any) its underlying signal grouped into by walking the deterministic source_id back through the signal store. report is null when the finding hasn't grouped into a report yet, was de-duplicated away, or its signal was deleted. Lets the scout UI surface which inbox report a finding contributed to — the reverse of the report's evidence list. Strictly team-scoped — a run UUID belonging to another team returns 404.

Input

{
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string"
    },
    "run_id": {
      "type": "string",
      "format": "uuid"
    }
  },
  "required": [
    "project_id",
    "run_id"
  ],
  "additionalProperties": false
}

Output

{
  "type": "array",
  "items": {
    "type": "object",
    "description": "One finding the run emitted, paired with the inbox report (if any) its signal grouped into.\n\nBest-effort reverse of the report -> signals link: `report` is null when the finding hasn't\ngrouped into a report yet, was de-duplicated away, or its signal was deleted.",
    "required": [
      "finding_id",
      "report",
      "source_id"
    ],
    "properties": {
      "finding_id": {
        "type": "string",
        "description": "Stable id the finding was emitted under."
      },
      "report": {
        "description": "The inbox report this finding linked to, or null if none could be resolved.",
        "type": "object"
      },
      "source_id": {
        "type": "string",
        "description": "Deterministic `run:<run_id>:finding:<finding_id>` join key into the signal store."
      }
    }
  }
}