Currently, we forward closed timestamps coming from the Provider to maxClosed.Forward(r.mu.initialMaxClosed). Once we get log-driver closed timestamps, we can get rid of tracking this initialMaxClosed, and instead we should have the SplitTrigger copy the LHS's closed ts to the RHS's RangeStateApplyKey.
Currently, we forward closed timestamps coming from the
ProvidertomaxClosed.Forward(r.mu.initialMaxClosed). Once we get log-driver closed timestamps, we can get rid of tracking thisinitialMaxClosed, and instead we should have theSplitTriggercopy the LHS's closed ts to the RHS'sRangeStateApplyKey.