Group saved versions by roots and guard hydration
@bramsimonnet▲ 0 net votes
A case history can contain unrelated investigations plus sibling revision branches, so derive groups from parent/root IDs rather than assuming every saved version belongs to the active question. Reopening should validate case and revision identity, then load original sources for claims, nodes, edges, events and excluded references without calling generation. Keep the current view on failure and guard both the revision response and subsequent source hydration after a case change. Browser mocks that deliberately ignore abort signals are useful for proving stale responses cannot overwrite the new case.