[Hackathon] fix(cli): help <typo> silently exits 0 inside command groups (root correctly exits 5) #418

Verified against (commit SHA or released version)

commit 988c035 (main HEAD; testsprite --version -> 0.14.0)

Discord Username / User ID

sati1325

What does this improvement do?

testsprite <group> help <typo> and testsprite <group> <typo> --help exit 0 and print the group's help, silently swallowing the misspelled subcommand — while the same shapes at root level correctly fail with exit 5 (error: unknown command '<name>'). The typo'd name is never reported.

Repro (no credentials needed):

$ testsprite help badcmd              -> exit 5, error: unknown command 'badcmd'   [correct]
$ testsprite test help badsub         -> exit 0, prints `testsprite test` help      [wrong]
$ testsprite test badsub --help       -> exit 0, prints `testsprite test` help      [wrong]
$ testsprite help test badsub         -> exit 0                                     [wrong]
$ testsprite project env help badsub  -> exit 0                                     [wrong]

Every command group behaves this way (test, project, project env, agent, ci, schedule, testlist, tunnel, auth, test code, test plan, schedule run). A script or agent that asks for a subcommand's help cannot tell — via exit code — whether that subcommand actually exists, and with --output json it gets a text help dump instead of the JSON VALIDATION_ERROR envelope.

Root cause: unknownRootCommandMaskedByHelp in src/index.ts runs inside an addHelpText('beforeAll') hook that bails unless context.command === program, so the unknown-command check only ever fires for root help. For group help, Commander's own "show parent help" fallback wins and throws commander.help -> exit 0.

Details / implementation notes

Fix generalizes the mask check into unknownCommandMaskedByHelp: walk the argument path down the command tree (skipping the argument of value-taking options like --output json), and report the first token that fails to resolve to a real subcommand whenever a help path is being rendered or a later --help/-h would mask the error. Covers help bad, <g> bad --help, <g> help bad, help <g> bad, and arbitrarily nested groups. Verified: valid help targets (test help run, test run --help, help test, project help env) still exit 0, and --output json emits the proper VALIDATION_ERROR envelope.

A PR with the fix + regression tests will follow referencing this issue.

Confirmations

• I have searched existing issues and this is not a duplicate.
• I have provided my Discord identity above for reward coordination.