CLI framework, positional syntax, help, and routing contracts

Keep commands focused on parsing, API orchestration, and CommandOutput; move substantial rendering to domain formatters. Async generators yield output and return hints only through CommandReturn. Command declarations and command-owned metadata are canonical for usage: preserve variadic ..., explicit compound syntax, and zero-positional or flag-only modes. Determine cardinality from runtime behavior, flags, tests, and semantic error contracts before adding parser minima. Shared builders must distinguish injected flags, preserve automatic output/--fresh behavior, and retain org/project targeting and list interception. Validate scanner, routing, help, version, metadata, and generated docs through real Stricli/application dispatch, including argument order, blank versus omitted values, --, global flags at multiple depths, output streams, exit codes, and regenerated artifacts.