agent simulation: record the CI pipeline a run came from

[u9g]

A simulation run currently has no record of where it came from. SimulationRun.Create.Request carries the project, agent, scenario group, mode and impairments, but nothing about the commit, branch, or pipeline that started the run — so a run created from a laptop and a run created by a merge queue are indistinguishable in the dashboard forever, and someone triaging a red run has no path back to the PR that caused it.

This adds a SimulationRun.CI message, set on Create.Request (field 13) and mirrored on SimulationRun (field 21) so it round-trips through GetSimulationRun and ListSimulationRuns.

It is named CI rather than Source because source already means the uploaded agent tarball in this same scope (ConfirmSourceUpload, ConfirmSimulationSourceUpload, and "description is derived from source"); a source field on SimulationRun would read as the tarball.

Both fields are optional — absent is the normal case for a run started from a laptop or the dashboard.

Downstream

First of four PRs, and the only one unblocked. The others need a github.com/livekit/protocol and @livekit/protocol release first:

• livekit/agents-private — persist it on the run row, return it on Get/List
• livekit/livekit-cli — populate it automatically from the GitHub Actions environment
• livekit/web — link a run back to its CI job on the run detail page

No SDK change is needed: agents (Python) and agents-js both alias the generated type verbatim (SimulationRun = proto.SimulationRun, and a plain re-export) and neither ever creates a run, so the field appears in both on a version bump.

Verification

mage proto, then go build ./... clean and go test ./livekit/... ./rpc/... passing.

[changeset-bot]

🦋 Changeset detected

Latest commit: 3e362fa

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
github.com/livekit/protocol	Patch
@livekit/protocol	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR