DESCRIBE PAGE output not guaranteed to roundtrip through mxcli check

[ako]

Problem

DESCRIBE PAGE output is not guaranteed to re-parse through mxcli check. (Microflow DESCRIBE roundtrip was fixed in v0.11.0 and is confirmed working; this is the remaining page case.)

Current behavior

There is no automated coverage of page DESCRIBE → check roundtrip: the page roundtrip tests (mdl/executor/roundtrip_page_test.go, //go:build integration) only assert the output contains expected widget names — they never feed the output back through the parser/check.

⚠️ Note for whoever picks this up — a tempting but WRONG hypothesis

During investigation it looked like the cause was DESCRIBE emitting snake_case action strings (show_page, call_microflow) while the grammar uses uppercase tokens (SHOW_PAGE, CALL_MICROFLOW). This is not the cause — the lexer uses case-insensitive fragments (fragment S: [sS] … in mdl/grammar/MDLLexer.g4:822+), so show_page tokenizes fine as SHOW_PAGE. Don't "fix" the casing and call it done.

The real breakage is structural (specific widget/action constructs the CREATE PAGE grammar doesn't accept in the shape DESCRIBE emits, and/or unquoted reserved-word identifiers — see #619). A concrete reproduction is needed first to identify which constructs fail.

Request

Guarantee DESCRIBE PAGE roundtrip, and add a roundtrip test that actually re-checks the DESCRIBE output (not just substring assertions).

---

Source: customer feedback batch (2026-06). Reporter: Miwa. Reporter severity: 5/5.
Filed after codebase investigation at 297e0b0a.

[github-actions]

Issue Triage

Summary:
The issue reports that the output of mxcli describe page cannot be reliably fed back through mxcli check (the round‑trip fails), and asks for a proper round‑trip test to guarantee correctness.

Checklist for bug report completeness

Required information	Present?	Notes
mxcli version (output of mxcli --version or commit/build)	❌	Not mentioned
Mendix version of the project being processed (e.g., 10.x, 9.x)	❌	Not mentioned
Scenario – what the user was trying to do (MDL script, CLI command, etc.)	❌	Only a general description; no concrete command or project context
Expected output – what should have happened	❌	Implied (round‑trip should succeed) but not explicitly stated
Experienced output – what actually happened (error message, wrong result, crash)	❌	No error message or failure details provided
AI bug report – output of mxcli diag --bundle or at least the session log	❌	Not included

Request for additional information
To help us investigate and fix the round‑trip issue, could you please provide:

1. The exact version of mxcli you are using (run mxcli --version or share the commit/build hash).
2. The Mendix version of the project you are working with.
3. A minimal example or steps to reproduce the problem (the exact mxcli describe page command you ran, and the resulting MDL snippet that fails when passed to mxcli check).
4. The expected behavior (e.g., “the DESCRIBE output should parse without errors”) and the actual error or output you observed when running mxcli check on that snippet.
5. If possible, the output of mxcli diag --bundle (or at least the relevant session log) so we can see the environment and any internal diagnostics.

Once we have those details, we’ll be able to pinpoint the structural breakage and add a proper round‑trip test. Thank you for bringing this to our attention!

---

Automated triage via OpenRouter — workflow source