feat(executions): add result_ref kwarg to report_outcome

[govindkavaturi-art]

Summary

The server's /v1/executions/{id}/outcome endpoint already accepts a result_ref evidence field (see OutcomeRequest in cueapi/cueapi app/schemas/outcome.py). The SDK's report_outcome was missing it, forcing callers who want to attach a reference ID to fall back to either raw HTTP or using an unrelated field like external_id.

Change

Single-line addition in cueapi/resources/executions.py: new optional kwarg, forwarded to the POST body when provided, same shape as every other evidence field.

@@ -58,6 +58,7 @@ class ExecutionsResource:
         metadata: Optional[dict] = None,
         external_id: Optional[str] = None,
         result_url: Optional[str] = None,
+        result_ref: Optional[str] = None,
         result_type: Optional[str] = None,
         summary: Optional[str] = None,
         artifacts: Optional[list] = None,
@@ -74,6 +75,8 @@ class ExecutionsResource:
             body["external_id"] = external_id
         if result_url is not None:
             body["result_url"] = result_url
+        if result_ref is not None:
+            body["result_ref"] = result_ref

Companion change

cueapi-worker 0.3.0 (released to PyPI 2026-04-17) exposes the same field on its WorkerAPIClient so worker-transport handlers can surface result_ref via the new CUEAPI_OUTCOME_FILE pattern. This SDK change closes the loop for direct (non-worker) callers.

Compatibility

No behavioral change for existing callers — kwarg is optional and defaults to None.

Test plan

• CI green
• Smoke: report_outcome(execution_id, success=True, result_ref="my-ref-123") POST body contains "result_ref": "my-ref-123"