A request’s checkpoint bounds resolved into the checkpoint-sequence
interval to scan. Unlike ResolvedRange/ResolvedEventRange, the
scan domain here is checkpoint space, so the entry and terminal
checkpoints derive from range directly and need no extra fields.
ResolvedRange’s analogue for event scans: the scan domain is
(tx_seq, event_index) coordinates, and the same two endpoint
checkpoints annotate it for watermark rendering (see ResolvedRange
for why they are not a Range).
A request’s checkpoint bounds resolved into the transaction-sequence
interval to scan, annotated with the checkpoint-space facts watermark
rendering needs.