Triage 9 pre-existing bug-test fixtures failing mxcli check

[ako]

After extending `make check-mdl` to cover `mdl-examples/bug-tests/` (commit 05fc1d3), 9 fixtures fail `mxcli check` and are currently skipped via a deny-list in the Makefile to keep CI green.

The failures are heterogeneous. Each needs individual triage:

Fixture	Likely cause
`116-datagrid2-column-name-mismatch.mdl`	Parse errors (syntax may demonstrate the bug intentionally)
`343-list-attribute-find-filter.mdl`	Probably needs project context (Attribute paths)
`352-java-action-return-type-inference.mdl`	Probably needs project context (Java action signature)
`352-retrieve-compact-reverse-association.mdl`	Probably needs project context (association paths)
`360-import-mapping-result-type.mdl`	Probably needs project context (mapping result type)
`367-retrieve-sort-indirect-entity-ref.mdl`	Probably needs project context (sort path)
`369-rest-mapping-result-cardinality.mdl`	Probably needs project context (REST mapping)
`373-change-action-items-storage-list.mdl`	Probably needs project context (entity attributes)
`552-npe-reserved-words.mdl`	Negative test — validator MUST fire on reserved-word attrs

Work

For each fixture:

1. Run `mxcli check` and triage the failure mode
2. If it requires a project, decide whether to run it with `-p ... --references` against a fixture project, or whether the fixture is genuinely demonstrating something `mxcli check` can't validate standalone
3. If it's a negative test (552), update the Makefile to invert the exit code expectation — these should fail check and be reported as PASS
4. If it's a "demonstrate broken syntax" fixture, consider splitting the bug demo (broken) from a fixed example (clean) so CI can cover the post-fix state

Once each is triaged and either fixed or properly categorized, remove its entry from the SKIP list in the Makefile's `check-mdl` target.

Acceptance

• All 9 fixtures removed from the SKIP list in `Makefile`
• `make check-mdl` covers them with appropriate semantics (positive or negative)
• No regression in coverage of other doctype-tests / bug-tests

[github-actions]

Issue Triage

Summary
The issue asks for triage of nine MDL fixture files that currently cause mxcli check to fail and are therefore skipped in the Makefile, with the goal of fixing or properly categorizing each one so they can be run in CI.

Checklist of required information (bug report)

Required info	Present?	Notes
mxcli version (output of mxcli --version or commit/build)	❌	Not provided
Mendix version of the project being processed	❌	Not provided
Scenario – what the user was trying to do (MDL script, CLI command, etc.)	⚠️ Partially	Mentions running mxcli check on fixtures, but no concrete command or context given
Expected output – what should have happened	❌	Not described
Experienced output – what actually happened (error message, wrong result, crash)	❌	Only says fixtures “fail mxcli check”; no error output shown
AI bug report – output of mxcli diag --bundle or at least the session log	❌	Not included

Next steps
To move forward, could you please add the following details?

1. The exact version of mxcli you’re using (e.g., mxcli --version output).
2. The Mendix version of the projects/fixtures you’re checking.
3. The precise command you run (including any flags like -p … --references).
4. The expected result for each fixture (e.g., “should pass” or “should fail with a specific validation error”).
5. The actual error messages or output you see when running mxcli check on each fixture.
6. If possible, a diagnostic bundle from mxcli diag --bundle (or at least the relevant session logs) for one or two representative failures.

Once we have that information, we’ll be able to triage the fixtures accurately. Thanks for your help!

---

Automated triage via OpenRouter — workflow source