[ako]

Syncs ako/mxcli:main into mendixlabs/mxcli:main: 5 commits since #1394, landed in the fork through PRs ako#1127–ako#1131.

diff-local (#1393)

• Headers name the unit and revision, with the module-qualified name, instead of Microflow.<uuid> (current) / (script). An MPR v2 .mxunit does not carry its container, so the module is now resolved from the project hierarchy.
• Pages, nanoflows and layouts render their bodies. A changed one counted as modified but printed no hunk, because the renderers emitted a fixed placeholder. Nanoflows were also dispatched to the microflow parser, because Microflows$Nanoflow contains Microflow.

Integration

• Export mapping members are written in message definition order (Export mapping: elements written in a different order than the schema are accepted, then mx check fails with CE5015 #1387). Script order gave CE5015 "The order of the schema elements … does not match the schema", including after alter message definition … add member. Measured on 11.12.1, the import and JSON-structure mappings check clean in either order, so only the export path changes.

Syntax lookup

• mxcli syntax grant / revoke / refresh resolve through the topics' keyword lists (mxcli syntax lookup misses common statement verbs (grant) and two-level names (integration message-definition) #1389). They answered "Unknown topic" before. A leading word that names a topic, followed by words that name another topic exactly, resolves to that topic (syntax integration message-definition).

Tests

• Pins both refusal shapes from check passes a create or modify microflow that exec refuses ("Nothing was written") when the flow calls a microflow created earlier in the same script #1361 for calls to flows the script itself creates (a variable clash, and an edit inside a loop body), each with a no-call control. The fix itself was in the previous sync

[github-actions]

AI Code Review

Critical Issues

None found.

Moderate Issues

None found.

Minor Issues

None found.

What Looks Good

The PR successfully addresses four distinct issues with appropriate fixes and test coverage:

1. diff-local (diff-local --ref a..b: header shows Microflow.<uuid>/(current)/(script), module dropped, and modified page prints no hunk #1393):

   • Fixed header naming to show module-qualified names instead of UUIDs
   • Implemented proper rendering of page/nanoflow/layout bodies using existing renderers
   • Corrected nanoflow dispatch order to check for nanoflow before microflow
   • Added comprehensive test coverage verifying header names and hunk generation

2. Export mapping order (Export mapping: elements written in a different order than the schema are accepted, then mx check fails with CE5015 #1387):

   • Implemented sorting of export mapping members by message definition order
   • Added test verifying schema order compliance and subset preservation
   • Maintained backward compatibility for import mappings and JSON-structure mappings

3. Syntax lookup (mxcli syntax lookup misses common statement verbs (grant) and two-level names (integration message-definition) #1389):

   • Enhanced topic resolution to check keyword lists for verbs like grant/revoke/refresh
   • Added qualified topic resolution (e.g., integration message-definition)
   • Improved error messaging with contextual headings for fallback matches
   • Added thorough test coverage for all new lookup scenarios

4. Test coverage for check passes a create or modify microflow that exec refuses ("Nothing was written") when the flow calls a microflow created earlier in the same script #1361:

   • Added test scripts pinning both refusal shapes (variable clash and loop body)
   • Included no-call controls to validate the fix
   • Verified the check command now properly predicts exec refusals

The changes follow established patterns:

• Uses existing rendering infrastructure (DESCRIBE-compatible)
• Maintains separation of concerns (executor/backend logic)
• Preserves backward compatibility where appropriate
• Adds tests at appropriate levels (unit, integration, MDL examples)
• Clear commit separation by concern
• Comprehensive comments explaining non-obvious logic

Recommendation

Approve the PR. The changes are well-implemented, thoroughly tested, and address the reported issues without introducing regressions or violating project guidelines. The fixes are minimal and focused, with appropriate test coverage to prevent future regressions. All checklist items have been satisfied.

---

Automated review via OpenRouter (Nemotron Super 120B) — workflow source