Module transaction_gate 

Startup recovery as a step of a wrapped or direct command. What: Startup recovery as a step of a wrapped or direct command: recover, then report how the command may go on. Why: Every command that reads the repository location recovers dead transactions first. A guarded command beside a live transaction is still refused until index writers coordinate with live transactions; a read-only command goes on. A legacy directory or a recovery failure stops the command with exit 2, as the incumbent’s content-unavailable engine failure does.

In TS you’d write (pseudocode):

await recoverCommitTransaction({ args, gitPath, identity }); // throws CommitTransactionRecoveryError

Enums

Gate

What: How a command may go on after recovery. Why: Callers refuse, stop or continue from this.

Functions

recover_for_command

What: Recover the invocation’s worktree and say how the command may go on. Why: Shared by wrapped commands, read-only commands and direct commands.