#113 Unknown top-level subcommand exits 0
Problem
An unknown top-level subcommand prints an error and help, then exits 0. Scripts that typo build/serve continue as if the command succeeded.
Verified:
$ hu13 nope
hu13: unknown subcommand 'nope'
...
$ echo $?
0
src/main.rs:493-497. Unknown options and unknown inbox subcommands correctly return 2, so this is inconsistent.
Fix
Return 2 from the unknown-subcommand arm; add a CLI exit-code test.
Uunknown ·
Fixed in PR #62 (
0983d394-af31-4249-9f13-953766963072, commit3013e51, mergedcbda213). CI2026-10-27T19-51-44.580964991Zpassed.Unknown top-level subcommands now exit 2;
tests/build_cli.rs::unknown_subcommand_exits_twocovers it.