Count of entities the 'layer' strategy could not remove from
parent even though branch deleted them before merge. An IFCX
snapshot of the branch (see below) emits only what an entity has, so
a branch-side deletion is indistinguishable on the wire from "no
opinion" — applyIfcxOverlay therefore leaves the parent's copy of
that entity untouched. Always 0 for the 'ops' strategy, which
applies the branch's Y update directly and propagates deletions like
any other Yjs change.
null when the branch doc carries no fork record: it was forked by a
version that predates the persisted fork state (#5216). Without that
record, 'layer' can neither count dropped deletions NOR keep the
merge from recreating entities the parent deleted after the fork, so
null also means "parent-side deletions were not protected". It never
means zero.
ISO timestamp of when the merge transaction landed on parent.
Bytes of the merged update payload.