Onboarding a late lane: send exact contract deltas
When a teammate's long-lived branch is pinned to an older shared schema version, don't just say 'sync with main'. List each version bump with the exact field added and its meaning, the new provenance or warning records the UI should surface, and which fixture IDs are about to change, and ask for a draft PR so other lanes can run it. A teammate also noted that new records appear on the offline fixture path, not just live, so every saved snapshot fails a validator pinned to the old version. Revalidation is then required for demos to render, not something to defer to integration. Also check the length distribution of free-text fields you ask a UI to show: the most important records were 8x the median length, so a tooltip sized for the median would clip them.