Multiple CLI commands exit 0 on error conditions

[retran]

Description

Several CLI subcommands exit with code 0 despite encountering errors or requiring arguments they don't have:

Command	Behavior	Expected
marketplace search <query>	Exits 0 on auth failure	Exit 1
eval list	Exits 1 but error message unclear (requires file arg, not documented)	Exit 0 with list, or clear help
widget init MyWidget	Requires -p flag not mentioned in help	Work standalone or clear error
tui without -p	"could not open a new TTY" instead of "required flag: -p"	Correct error message

Expected

Non-zero exit codes on all error conditions. Clear error messages indicating what's wrong.

Severity

Low — affects CI/scripting reliability.

Reproducing test cases

• cli-commands-test-cases.md § 7.5, 8.1, 4.2, 9.3, 15.2

[github-actions]

Issue Triage

Summary:
The issue reports that several mxcli subcommands incorrectly return exit code 0 (or give unclear messages) when they encounter errors or missing arguments.

Checklist of required bug‑report information

Required info	Present?	Notes
mxcli version (mxcli --version or commit/build)	❌	Not mentioned
Mendix version of the project being processed	❌	Not mentioned
Scenario – what the user was trying to do (specific CLI command/context)	✅	Described in the table (e.g., marketplace search, eval list, etc.)
Expected output – what should have happened	✅	Listed in the “Expected” column
Experienced output – what actually happened (error message, wrong result, crash)	✅	Described in the “Behavior” column
AI bug report – output of mxcli diag --bundle or session log	❌	Not provided

What’s missing:
Please add the mxcli version you’re using, the Mendix version of the project you’re working with, and, if possible, a diagnostic bundle (mxcli diag --bundle) or at least the relevant session log. This will help us reproduce and fix the behavior.

Thanks for bringing this to our attention!

---

Automated triage via OpenRouter — workflow source