Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
TelemetryArea: what it touches
Internal ChangesKind: in v2.1.280,
Internal ChangesSection of the release
What
Internal telemetry that compares model capability lists now reports picker_set_match, picker_added, and picker_removed from a richer underlying object, and adds two new fields: picker_full_match and served_overflow_count. The detailed before/after picker payloads (picker_old/picker_new) are now only included when either the base or the full picker set doesn't match.
Why
This gives more precise internal visibility into when the list of models shown to users diverges from what's expected, and avoids sending the full payload for comparisons that already match, trimming unnecessary telemetry data.
