Module management 

The git cli-git decision: help, retired commands, and direct check/fix. What: Decide what one git cli-git ... invocation does. Why: Help, refusals and retired commands need no repository; check and fix validate their policy selection and configuration, then run one policy pass over the selected repository and report its events on standard output.

In TS you’d write (pseudocode):

// const action = planManagement(managementArgs, gitGlobalArgs, controls, environment, inputs);

Functions

plan_management

What: Decide the action for the arguments after git cli-git. &[OsString] borrows argument lists; &Controls borrows what the wrapper controls written before cli-git asked for; &ResolutionInputs borrows process facts. Why: Help, refusals and retired commands answer without resolving Git or reading any repository. A direct command validates its selection, asks Git once where it runs, refuses beside commit transactions it cannot recover, loads that worktree’s configuration and runs one policy pass.

retired_explanation

What: Explain that a trust command is retired. String is the owned, line-terminated explanation. Why: Trust existed to approve executing a repository’s configuration code. JSONC configuration is data, so there is nothing to approve, revoke or report. Old trust records are neither read nor deleted.