[boks1971]

An agent worker cannot tell the server the time of each step of an agent join. The server sees only two points: the job offer and the agent joining the room. This PR adds a place for the worker to report the steps between those two points.

Change

UpdateJobStatus gets a new field, join_timing, of the new message JobJoinTiming. After the agent connects to the room, the worker sets it once.

Field	The worker reads its clock at this point
offer_received_us	the job offer arrives
accepted_us	the worker accepts the job
assignment_received_us	the job assignment arrives
launched_us	a job process gets the job
launch_warm	true: an idle process took the job. false: the worker started a new one, and launched_us also covers the agent's prewarm function
entrypoint_started_us	the agent entrypoint starts
connect_called_us	the agent calls connect
connected_us	the agent's WebRTC connection is up

The values are instants on the worker host's monotonic clock, in microseconds. The server can subtract them from each other directly. To line them up with its own times, the server needs a clock offset, for example from the offer and accept round trip. The change only adds fields, so old servers and old workers keep working.

🤖 Generated with Claude Code

[changeset-bot]

🦋 Changeset detected

Latest commit: 619a57f

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

[theomonnom]

Suggested change

	int64 prewarm_started_us = 6; // the agent's prewarm function, in the process that took the job
	int64 prewarm_ended_us = 7;

[theomonnom]

IMO we can remove those two, they're going to get removed in 2.0

[boks1971]

Will do @theomonnom . We can add it later if it fits in a different bucket.