Module feature_flags 

Stage-based feature flagging primitives (readiness gating), distinct from flags. Stage-based feature flagging primitives.

These types describe readiness gating: a command, group, or module can declare the Stage at which it becomes visible, and a run-wide FlagPolicy decides whether that stage (or an override for a specific flag key) is currently enabled.

Structs

FeatureFlag

A named feature flag: a key (used for policy overrides and introspection) paired with the stage at which the flagged node becomes visible.

FlagEntry

One flagged node discovered while pruning a command tree.

FlagPolicy

The fully-merged decision inputs for one CLI run: the minimum stage required for a node to be visible, plus any per-key overrides that force a specific effective stage regardless of the node’s declared stage.

FlagRegistry

Every flagged module/group/command path discovered while pruning a command tree, in registration order.

ParseStageError

Error returned when parsing an unknown feature stage.

Enums

Stage

Feature readiness stage, used to gate commands/groups/modules before they are fully promoted to general availability.