Function build_module_group 

pub fn build_module_group(module: &Module) -> RuntimeGroupSpec

Materializes a module’s command tree standalone, outside a running Cli.

Builds a throwaway Middleware and runs the module’s registration function against it — the same call Cli::new makes — so callers can walk the real RuntimeGroupSpec — e.g. to derive a scope→command registry from CommandSpec::metadata — without duplicating each module’s command declarations. Guides and views the module registers via ModuleContext are discarded; only the command tree is returned.

Unlike mounting a module through Cli::new/add_module, this does not apply feature-flag pruning: the returned tree includes every node regardless of the active FlagPolicy, so it may contain commands or groups that are actually hidden at runtime. Fine for callers that only need the static declarations (e.g. scope metadata), but don’t treat the result as “what’s mounted right now.”