Problem
Running charter adf <subcommand> --help (e.g. charter adf sync --help, charter adf migrate --help) renders the root charter --help output rather than documentation for the subcommand.
The actual per-subcommand docs are only accessible by running charter adf with no arguments.
Reproduction
$ charter adf migrate --help
# → outputs root charter --help
$ charter adf sync --help
# → outputs root charter --help
$ charter adf
# → outputs the correct subcommand reference (migrate, sync, fmt, patch, etc.)
Expected behavior
charter adf <subcommand> --help should output the specific documentation for that subcommand — equivalent to the relevant block from charter adf.
Alternatively, charter adf --help could output the full subcommand reference (which charter adf currently does).
Impact
Discoverability friction: the natural discovery path (command --help) doesn't work for ADF subcommands. Users hitting this for the first time won't find the docs until they run the bare charter adf form.
Problem
Running
charter adf <subcommand> --help(e.g.charter adf sync --help,charter adf migrate --help) renders the rootcharter --helpoutput rather than documentation for the subcommand.The actual per-subcommand docs are only accessible by running
charter adfwith no arguments.Reproduction
Expected behavior
charter adf <subcommand> --helpshould output the specific documentation for that subcommand — equivalent to the relevant block fromcharter adf.Alternatively,
charter adf --helpcould output the full subcommand reference (whichcharter adfcurrently does).Impact
Discoverability friction: the natural discovery path (
command --help) doesn't work for ADF subcommands. Users hitting this for the first time won't find the docs until they run the barecharter adfform.