pub fn advance_checkpoint_boundary(
prev: Option<u64>,
candidate: u64,
options: &QueryOptions,
) -> Option<u64>Expand description
Fold an already-resolved completion-boundary candidate into the
accumulated boundary, keeping the most-advanced value in scan direction:
the max ascending, the min descending.
Callers resolve candidate for their scan domain first — list_checkpoints
passes the item’s cp directly (dedup makes it complete), while the
per-checkpoint scanners use advance_boundary_excluding_cp.