[Akhil Gupta (akhil9tiet)]

Fixes #1015. Parse errors that print help (e.g. winapp cert bogus) exited with code 0, so scripts and agents treated them as success. InvokeAsync() displays the error and help text; this ensures the exit code is 1 when ParseResult.Errors is non-empty, matching the ui subcommands' behavior.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[Copilot]

🟡 Changes recommended

The new await is inside a non-async lambda, causing Release builds and tests to fail compilation.

2 open findings

• Mark telemetry callback async to fix compilation errors · New
• Add regression test for unknown subcommand help path · New

🧠 Review effort: Balanced

[Akhil Gupta (akhil9tiet)]

Added missing await.

[Akhil Gupta (akhil9tiet)]

Follow-up to the Cli-2 failure: the only failing test was TelemetryTests.HostInvocation_PreservesOptOutAndDoesNotTreatArgumentValuesAsGuestMode — winapp --json run --help --args guest-agent must exit 0 (help request honoured), but the blanket parse-error → exit 1 override flipped it to 1. Commit 9b66209 exempts help / CLI-schema requests from the override (detected from the matched options, so it holds whether the parser selected the help action or a parse-error action). The cert bogus case from #1015 is unaffected (no --help, still exits 1), and the InvokeWithHelpPointerAsync override is unchanged.