Under the hood
Session-start telemetry now checks whether the session's starting point is orphaned before firing
What
The telemetry call that fires when a session starts now first runs through a helper that determines whether the session's starting point (its 'head') is 'orphaned', and passes that status along with the event, instead of always firing unconditionally.
Why
This lets session-start tracking distinguish sessions that resume from a disconnected or missing starting point from normal ones, which is useful for diagnosing session continuity issues.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What exactly counts as an 'orphaned' session head is not specified in the evidence.