DROP ENUMERATION with ambiguous unqualified name silently drops one

[retran]

Impact

Drops the wrong enumeration without warning. User loses data with no recovery path.

Steps to Reproduce

1. Create Mod1.Status and Mod2.Status enumerations
2. Run DROP ENUMERATION Status;
3. One enumeration silently dropped — no ambiguity error

Expected Behavior

Error requiring fully-qualified name when multiple matches exist.

Severity

Medium — silent destructive action on ambiguous input.

---

Discovered during AI-assisted manual testing session (2026-04-29, mxcli v0.7.0-257-ga07e7e0).

[github-actions]

Issue Triage

Summary:
The issue reports that DROP ENUMERATION with an unqualified name silently drops one of multiple matching enumerations instead of erroring out.

Checklist for bug report completeness

Required info	Present?	Details
mxcli version	✅	v0.7.0-257-ga07e7e0 (from the note)
Mendix version	❌	Not mentioned
Scenario (what the user was trying to do)	✅	Creating two enumerations (Mod1.Status, Mod2.Status) and running DROP ENUMERATION Status;
Expected output	✅	Error requiring a fully‑qualified name when multiple matches exist
Experienced output	✅	One enumeration silently dropped, no ambiguity error
AI bug report (mxcli diag --bundle or session log)	❌	Only a general note about the testing session; no diagnostic bundle or log provided

Missing information:

• The Mendix version of the project being processed.
• The output of mxcli diag --bundle (or at least the session log) to help reproduce the environment.

Could you please add the Mendix version and attach the diagnostic bundle or session log? Thanks for reporting this!

---

Automated triage via OpenRouter — workflow source