Under the hood
History-upload telemetry can now log under different event names, not just fork_conversation
What
The internal helper that uploads a session's transcript history to a remote session, and reports telemetry when events get dropped in the process, used to always log under the fixed name rc_fork_conversation. It now takes the event name and a caller-supplied label as parameters instead, so different callers can report under different names.
Why
This lets other features besides conversation forking reuse the same history-upload code while still getting accurate, correctly-labeled telemetry.