DESCRIBE emits action: call_microflow/call_nanoflow for widget actions, which the parser rejects (roundtrip break)

[ako]

Summary

DESCRIBE on a page/snippet emits widget actions as action: call_microflow X / action: call_nanoflow X, but the MDL parser only accepts action: microflow X / action: nanoflow X (no call_ prefix). The emitted MDL fails to re-parse, breaking the "DESCRIBE roundtrip" guarantee for any page/snippet containing an action button (or other action-bearing widget).

Reproduction

create module RT;
create snippet RT.S ( params: { $C: ConversationalUI.ChatContext } ) {
  container c1 { actionbutton b (caption: 'X', action: call_nanoflow RT.N) }   -- as emitted by DESCRIBE
}

$ mxcli check repro.mdl
  - line 3:69 extraneous input 'RT' expecting {',', ')'}

Same failure with action: call_microflow RT.N.

The accepted forms pass:

actionbutton b (caption: 'X', action: nanoflow RT.N)    -- ✓ Syntax OK
actionbutton b (caption: 'X', action: microflow RT.N)   -- ✓ Syntax OK

Real-world trigger

describe snippet OntologyViewer.Snippet_ChatContext_Interaction emits:

actionbutton btnUseSuggestedUserPrompt (
  ...
  Action: call_nanoflow ConversationalUI.ACT_ChatContext_ExecuteSuggestedUserPrompt,
  ...
)

which fails mxcli check. The same applies to the FullScreenChat page and any artifact with call_microflow/call_nanoflow button actions.

Expected

Either (a) DESCRIBE should emit action: microflow X / action: nanoflow X (matching the parser), or (b) the grammar should also accept the call_ prefix. (a) is the lower-risk fix.

Environment

mxcli built from current main; reproduced via mxcli check (syntax only, no project needed).

[github-actions]

Issue Triage

Summary:
The DESCRIBE command emits widget actions with a call_ prefix (e.g., action: call_nanoflow X), which the MDL parser rejects, breaking the DESCRIBE‑roundtrip for pages/snippets that contain action buttons.

Checklist for bug report completeness

Required info	Present?	Details
mxcli version (output of mxcli --version or commit/build)	❌	Only mentions “built from current main”.
Mendix version of the project being processed	❌	Not mentioned.
Scenario – what the user was trying to do (MDL script, CLI command, etc.)	✅	Describes using DESCRIBE on a page/snippet then running mxcli check.
Expected output – what should have happened	✅	Either DESCRIBE should emit action: microflow X / action: nanoflow X or the parser should accept the call_ prefix.
Experienced output – what actually happened (error message, wrong result, crash)	✅	Shows mxcli check error: “extraneous input 'RT' expecting {',', ')'}”.
AI bug report – output of mxcli diag --bundle or at least the session log	❌	Not provided.

What’s needed:
Please add the exact mxcli --version (or commit/hash) you used, the Mendix version of the project you’re working with, and, if possible, the output of mxcli diag --bundle (or at least the relevant session log) so we can reproduce the environment precisely.

Thanks for reporting the issue! Once we have those details we’ll be able to investigate further.

---

Automated triage via OpenRouter — workflow source