Fix Wrong Exception on Cli run when Command Not found

[Genaker]

Before Fix error on Cli run:

After :

Description (*)

If you have ever tried to run bin/magento and been greeted with the maddening: "There is no command found in the namespace"

you already know how opaque Magento (Adobe Commerce) can be when a single CLI command class is broken. One constructor typo, a missing dependency, or a bad module upgrade and—boom—the whole console goes dark. No stack-trace, no filename, no clue. You are left spelunking through logs or disabling modules by trial and error. More than 10 years Adobe is not able to fix this critical issue! I'm tired and submitted the PR.

What My PR tiny but vital quality-of-life improvement:

• Catches the original exception thrown while Magento is assembling its command list.

• Prints the real message and class name before the fallback “no command found” notice.

• The change is only a few lines, but the impact is huge: you immediately see which command class failed and why, so you can fix the root cause in minutes instead of hours.

Why every extension author & integrator should care:

• Faster CI/CD – Broken modules fail loudly during automated builds; no more silent time-outs.

• Happier merchants – Support teams pinpoint faulty third-party code instead of asking store owners for full backups.

• Lean core – The patch touches only CLI bootstrap code; zero risk to storefront performance.

Thanks for backing real-world developer experience improvements—your click today could save countless debugging hundreds hours tomorrow!

Related Issue

[m2-assistant]

Hi @Genaker. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

---

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.