pub fn read_next_capture_sequence(git_dir: &Path) -> Result<i64, CaptureError>Expand description
What:
The next capture sequence number the store would allocate,
read without the lock;
an
absent store or sequence file reads as 1.
Why:
readNextCaptureSequence:
landings record it after their compare-and-swap.
In TS you’d write (pseudocode):
async function readNextCaptureSequence(gitDir: string): Promise<number>;