feat(tracing): stamp sgp evals run and row ids on SGP spans

[mohammadatallah-scale]

OVE-1253. Pairs with an sgp-evaluations PR that tags each generation-unit task.

The problem. Spans of an evals generation-unit task carry no run or row id, so a spans search cannot find them.

The fix.

• Stamp: the SGP copy of each span of an eval task gets flat run, row and attempt keys. A task that loses the eval marker stops being stamped.
• Sync and async agents: the ACP server reads the task it receives.
• Temporal agents: the ids travel through the workflow memo to the worker's activities. A span keeps the ids its task had when it started, so a reused task id cannot strip a queued span. Not covered: spans whose trace_id and task_id are both not the task id.

Test plan

• Real Temporal dev server run: eval workflow stamps the three keys, a plain one stamps nothing

Changes since review

• A span's run and row ids are fixed when it starts, so a task id reused before export cannot change them.
• A span that started with no eval task can no longer pick up a later run's ids.
• A failed upload keeps the ids, so a retry sends the same span.

Confidence Score: 5/5

This update appears safe to merge; no new issue remains to address.

What we checked:

• Plain spans evict saved eval IDs: No. Plain captures use a separate map, and the test checks that the eval capture remains after the plain map exceeds its limit.

Summary

SGP eval task run, row, and attempt ids now appear as searchable metadata on the task’s spans. The PR passes those ids through both in-process ACP handlers and Temporal workers, and keeps each span’s attribution fixed from start through upload.

• SGP eval spans carry searchable run, row, and attempt ids.
• Temporal activities carry eval ids into their spans.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
    A[Task metadata] --> B[Task ID registry]
    B --> C[Capture IDs when span starts]
    C --> D{Captured IDs?}
    D -->|Yes| E[Eval span map]
    D -->|No| F[Plain span map]
    E --> G[SGP export]
    F --> G
    G --> H[Release capture after export]

Loading

_{Reviews (5) · Last reviewed commit: "fix(tracing): keep eval span id captures..." · Reviewed by Greptile}

[mohammadatallah-scale]

P3 sgp_evals_interceptor.py - activities of a child workflow get no header (memo is not inherited and their workflow id is not the task id), so their spans stay unstamped even when trace_id is the task id.
P3 worker.py:278 - no test pins SGPEvalsInterceptor in the worker's interceptor list, so dropping it keeps the suite green.

Refuted: continue-as-new keeps the memo (real dev-server run stamps the post-CAN run), ContextInterceptor headers coexist with this one in either order, and task_metadata does reach the agent inside params.task, so the event/send pop never drops a live eval task.