pub fn replay_commit(
request: &ReplayRequest<'_>,
) -> Result<ReplayOutcome, ReplayError>Expand description
What:
Replays the prepared commit onto current:
lists the shared paths, decides capture order, settles subsumed paths, merges, and rebuilds on a clean merge;
on a conflict, names the first landed commit that touched a conflicting path.
Why:
Every step runs outside both landing locks in the shadow store, so the landing loop can take the locks only for the
revalidated commit it then lands.
In TS you’d write (pseudocode):
// replay in commit-replay.ts; order decisions and subsumption composed as the landing step does