Module commit_revalidation 

Revalidation of a replayed tree outside both landing locks. What: Revalidation of a replayed tree, outside both landing locks: a private index for the replayed tree, the shadow HEAD at the replay parent, the policies converged again over that index, and pre-commit re-run whenever the tree differs from the one it last approved. Why: A replay merges changes the policies and the hook never saw together, so the merged tree must pass the same gates as the prepared one (src/policy-engine/commit-revalidation.ts).

In TS you’d write (pseudocode):

const revalidation = await revalidateReplay({ context, replay, mergedTree, onto, approvedTree });

Structs

RevalidationContext

What: What revalidation reads besides the policies. Why: The hook re-run needs the kept global options and the shim; the policies need the capture.

Enums

Revalidation

What: The result of revalidating a replayed tree. Why: A blocked tree stops the commit with the policies’ events; a revalidated one is rebuilt and landed.

Functions

ensure_replay_directory

What: Make the directory of one replay, accepting one that subsumption already made for its base index. Why: Every other failure leaves the replay without a place for its index.

is_detached

What: Whether the invocation started on a detached HEAD. Why: A detached replay moves the shadow HEAD itself; a branch replay moves the branch.

revalidate_replay

What: Revalidate a replayed tree. Why: The policies converge over the replayed index with the replay parent as their baseline, and pre-commit sees the tree when the policies changed what it last approved.