Module escape_hatch 

Spellings of the wrapper-only escape hatches shared by several modules. What: The spellings of the wrapper-only escape hatches several modules share. Why: A command module puts its own hatch first in the flag list it hands the option tokenizer, and the control table lists the same spellings; one constant per spelling keeps both in step. Removal is not done here: wrapper_invocation.rs deletes wrapper tokens by the positions the tokenizer reports.

In TS you’d write (pseudocode):

// export const WORKTREE_ENFORCEMENT_ESCAPE_HATCH = '--no-enforce-worktree';

Constants

BRANCH_WORKTREE_ESCAPE_HATCH

Wrapper-only flag suppressing worktree-first branch creation enforcement for one branch, checkout or switch invocation.

WORKTREE_COPY_ESCAPE_HATCH

Wrapper-only flag skipping ignored-state synchronization into new worktrees.

WORKTREE_ENFORCEMENT_ESCAPE_HATCH

What: Wrapper-only flag suppressing linked-worktree enforcement for one invocation. &str is borrowed text; here it is baked into the program. Why: git stash, git clean and git reset name it as their own hatch.