DESCRIBE ASSOCIATION emits DELETE_CASCADE but parser only accepts CASCADE

[retran]

Impact

Association DESCRIBE output is not roundtrippable. Drop-and-recreate workflows break with a parse error.

Steps to Reproduce

1. Create an association with delete_behavior CASCADE
2. Run DESCRIBE ASSOCIATION Module.Name
3. Output contains delete_behavior DELETE_CASCADE
4. Drop the association
5. Re-execute the DESCRIBE output verbatim
6. Parser rejects DELETE_CASCADE — expects CASCADE

Expected Behavior

DESCRIBE output uses the same token the parser accepts (CASCADE), making output roundtrippable.

Severity

High — breaks any automated roundtrip or migration workflow.

---

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

[github-actions]

Issue Triage

Summary:
The DESCRIBE ASSOCIATION command outputs delete_behavior DELETE_CASCADE, which the parser cannot accept (it expects CASCADE), breaking round‑trip workflows.

Checklist for bug report completeness

Required info	Present?	Details
mxcli version	✅	v0.7.0-257-ga07e7e0 (mentioned in the issue)
Mendix version	❌	Not specified
Scenario (what the user was trying to do)	✅	Creating an association, running DESCRIBE ASSOCIATION, dropping and re‑executing the output
Expected output	✅	DESCRIBE should emit delete_behavior CASCADE so the output can be re‑parsed
Experienced output (error/wrong result)	✅	DESCRIBE emits DELETE_CASCADE; parser rejects it, expecting CASCADE
AI bug report (session log or mxcli diag --bundle)	❌	No log or bundle provided

Missing information
Could you please add the Mendix version of the project you’re working with and, if possible, attach the session log or output of mxcli diag --bundle? This will help us reproduce and fix the issue more quickly. Thank you!

---

Automated triage via OpenRouter — workflow source