Module management_arguments 

The git cli-git argument grammar. What: The grammar of git cli-git <command>, the wrapper’s own management namespace. Why: check and fix run policies over an explicit scope; trust, untrust and status are retired with executable configuration and only explain that.

In TS you’d write (pseudocode):

// parseManagementArgs(['check', '--all']) => { command: 'check', all: true, policies: [], pathspecs: [] }

Enums

ManagementAction

What: One understood management invocation. Vec<String> is an owned list of owned UTF-8 text; Vec<OsString> keeps raw bytes. Why: The runner acts on a typed value; nothing downstream re-reads raw arguments.

ManagementRefusal

What: Why a management invocation was refused. Why: Each refusal has its own remedy, so each has its own message.

RetiredCommand

What: The three commands that existed only to approve executable configuration. #[derive(...)] generates copying, debug printing and ==. Why: Each still parses, so old instructions get an explanation instead of a usage error.

Constants

MANAGEMENT_HELP

Successful namespace help, shown without touching any repository.

MANAGEMENT_USAGE

What: The complete grammar shown when an invocation is refused. &str is borrowed text compiled into the executable. Why: The text states the enforced rule: exactly one scope per direct command.

Functions

parse_management_arguments

What: Parse the arguments after git cli-git into one action or refusal. Why: The leading command name selects one grammar, so an invocation naming two commands is refused for its stray argument rather than guessed at.