Annotate dt CI spans with GitHub run/job identity

Context

Downstream CI users can query recent dt / dt-task traces, but the current span schema is missing GitHub CI identity. That makes it hard to do historical performance analysis or correlate trace regressions back to a specific workflow run/job without falling back to GitHub Actions APIs.

Concrete downstream example: livestorejs/livestore#1127 is investigating CI slowdown over time. The current OTEL data is useful for short-term task breakdowns, but not for reliable CI forensics.

Current behavior

dt spans carry task-level data like dt.args, and dt-task spans carry execution/cache data like task.cached and exit.code.

However, CI runs do not appear to annotate spans with GitHub metadata such as:

• github.run_id
• github.job
• github.workflow
• github.run_attempt
• optionally git.branch / git.sha / repo

Those values are available in the CI environment already, but today they are only echoed into logs/diagnostics, not attached to traces.

Desired behavior

When dt / dt-task spans run under GitHub Actions, annotate them with stable CI identity attributes so traces can be filtered and trended by workflow/job/run.

Minimum useful set:

• github.run_id
• github.job
• github.workflow
• github.run_attempt

Likely also useful:

• github.repository
• git.branch
• git.sha
• ci=true

Why this matters

This would let downstream repos use Grafana/Tempo as a real CI performance dataset instead of only a short-lived debugging view. It would also make dashboards like dt-tasks and dt-duration-trends much more actionable for regressions.

Notes

This is complementary to retention improvements. Even with longer Tempo retention, the current schema is still too weak for robust CI trend analysis.

Related downstream context:

• https://github.com/livestorejs/livestore/issues/1127

Acting on behalf of the user.

Start by locating where dt and dt-task spans are created, then trace the existing GitHub Actions environment handling used for logs or diagnostics. Confirm which GitHub metadata variables are available there and how span attributes are tested. Done means GitHub Actions spans carry the required run, job, workflow, and attempt identity attributes, with optional repository and Git fields if supported.