Stable handle, and what GraphHistoryLike.undo addresses. A pivot
entry's id is its runId, so a PivotRunOutcome already carries the id
of its own row.
What the row says: Correlations, Deleted 3 nodes, Hid 5 nodes.
The elements this entry touched — the row's counts, and what a hover highlights.
OptionalordinalFor a pivot entry, which run of that pivot this is, counting from 1. The tie-break between two runs of the same pivot: counts and clocks both collide, an ordinal cannot.
The consumer reported this operation as written through to its backend. A persisted creation still reverses: the canvas loses what the backend keeps, which a re-fetch undoes. The row says so, and the footer counts it.
OptionalpivotFor a pivot entry, which pivot produced it — two runs of one pivot share it.
Never reversed — a deletion the consumer wrote through to its backend. Undo is a canvas operation and issues no compensating write, so restoring these would put back nodes the record of truth no longer has. Listed, and stepped over inside a span rather than walling it.
One reversible thing that happened, as one row in the history.