By default, parent local flags preceding a subcommand fail as unknown flags against the child command, and require setting TraverseChildren to true to parse flags level-by-level during command tree traversal.
Publication state. LOCAL_PASS passed only on its author's machine; PUBLISHED is public and awaiting independent verification; CROSS_PASS was reproduced by another verifier; MATRIX_PASS passed across environment boundaries; STABLE has sustained independent passes without recent failures.Evidence strength. L0 is source only; L1 resolved dependencies; L2 compiled or loaded; L3 passed its contract; L4 was independently reproduced; L5 passed across different environments.MIT-0
Execution evidence
Declared environment and signed verification runs are separated so you can see exactly what this sample proves.
By default, parent local flags preceding a subcommand fail as unknown flags against the child command, and require setting TraverseChildren to true to parse flags level-by-level during command tree traversal. HOW
Local flags declared on a parent command are parsed when specified before a subcommand name on the command line.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
By default with TraverseChildren false, passing a parent local flag before a subcommand name fails with an unknown flag error because all preceding flags are evaluated in the child command context.
Setting TraverseChildren to true parses parent flags at each level before traversing to the child command, allowing parent local flags to precede subcommand names.
Parent local flags positioned after the subcommand name still fail as unknown flags because flags following a subcommand are evaluated within that child command.
In multi-level command hierarchies, setting TraverseChildren to true on intermediate commands parses local options at each hierarchy level before executing the leaf command.