Daily Digest: 2026-05-05

[github-actions]

We are given a daily digest for 2026-05-05. We need to structure the response as:

1. Highlights (1-3 bullet points of the most important changes)
2. Code Changes (summarize commits by theme, not individually)
3. Pull Requests (merged, opened, pending review)
4. Issues (new, closed, total open)
5. Repository Health (stars, forks, CI status)
6. Action Items (anything that needs attention: failing CI, stale PRs, unanswered issues)

Let's break down the provided data:

Repository Stats

• Stars: 77
• Forks: 25
• Watchers: 7
• Open issues: 1 (but note: the issues section lists several opened and closed, so we'll see)

Commits (last 24h)

There are many commits. We need to summarize by theme.

Looking at the commits:

• Refactor: split MDLParser.g4 into domain-specific files (f96a037) -> related to issue Split MDLParser.g4 by domain to reduce grammar merge conflicts #515
• Chore: release v0.8.0 (0d6ddd5)
• Fix: make macOS Applications dir mockable to fix test isolation (9c73fce)
• Fix: resolveSnippetRef now checks session cache before querying backend (446ba69) -> fixes fix: resolveSnippetRef ignores in-session cache, causing forward snippet references to fail #509
• Docs: add resolve-forward-references skill; fix OR REPLACE bug in overview-pages (b385a57)
• Merge PR fix: address merged microflow review followups #408 (74595ec)
• Merge PR feat: allow expressions in add-to-list statements #362 (5a5b743)
• Docs: add proposal for agentic architecture improvements and conflict reduction (0c374cf)
• Fix: mxcli new fails on macOS with exec format error (Studio Pro lookup) (81a0b35)
• Feat: extend VS Code extension and LSP to cover all document types (dfa025c)
• Merge PR fix: resolve JSON structure qualified-name lookup through folder hierarchy #508 (097a799)
• Merge PR fix: loop-back retry error handler to merge before source activity (#506) #507 (1eeef12)
• Test: regression test for folder-nested JSON structure lookup (733e10f)
• Fix: resolve JSON structure qualified-name lookup through folder hierarchy (7a2832e)
• Fix: loop back retry-style error handler tail to a merge before the source (25fde3d)
• Fix: track add-to-list expression vars in error-handler statement refs (fa1c909)
• Merge PR fix: rejoin empty custom error handler at IF ELSE first activity #504 (4270259)
• Fix: rejoin empty custom error handler at IF's ELSE first activity (b351068)
• Update Mendix versions in nightly workflow (29779d6)
• Merge PR fix: preserve cross-module associations on CREATE object actions #502 (dc7ef0d)
• Update Mendix version to include 11.10.0 (be31b60)
• Fix: preserve cross-module associations on CREATE object actions (efeefea)
• Fix: honor UseReturnVariable when emitting call-action assignments (1568e64)
• Fix: use valid add-to-list expression fixture (a0c3ef4)
• Fix: track add-to-list expression inputs (0f3fbe3)
• Feat: allow expressions in add-to-list statements (6d7b92c)
• Fix: address merged microflow review followups (76e1989)
• Fix: SET format = json now takes effect for subsequent statements (d73e9c9) -> fixes REPL: SET key = value listed in HELP but not implemented (scaffolding only) #471
• Fix: implement session-level SET key = value command (96cecc3) -> fixes REPL: SET key = value listed in HELP but not implemented (scaffolding only) #471
• Fix: CATALOG.ASSOCIATIONS/CONSTANTS/OBJECTS returning no rows (issue CATALOG.ASSOCIATIONS table missing from catalog #419) (7a45dc2) -> fixes CATALOG.ASSOCIATIONS table missing from catalog #419

We can group the commits by theme:

1. Parser and Grammar Refactoring:

   • Split MDLParser.g4 into domain-specific files (f96a037) [related to issue Split MDLParser.g4 by domain to reduce grammar merge conflicts #515]

2. Release and Versioning:

   • Release v0.8.0 (0d6ddd5)
   • Update Mendix versions in nightly workflow (29779d6)
   • Update Mendix version to include 11.10.0 (be31b60)

3. macOS Specific Fixes:

   • Make macOS Applications dir mockable to fix test isolation (9c73fce)
   • Fix mxcli new fails on macOS with exec format error (81a0b35)

4. Snippet Reference and Caching:

   • resolveSnippetRef now checks session cache before querying backend (446ba69) [fixes fix: resolveSnippetRef ignores in-session cache, causing forward snippet references to fail #509]

5. Documentation:

   • Add resolve-forward-references skill; fix OR REPLACE bug in overview-pages (b385a57)
   • Add proposal for agentic architecture improvements and conflict reduction (0c374cf)

6. VS Code Extension and LSP:

   • Extend VS Code extension and LSP to cover all document types (dfa025c)

7. JSON Structure Lookup:

   • Regression test for folder-nested JSON structure lookup (733e10f)
   • Fix: resolve JSON structure qualified-name lookup through folder hierarchy (7a2832e)

8. Error Handler and Microflow Fixes:

   • Loop back retry-style error handler tail to a merge before the source (25fde3d)
   • Track add-to-list expression vars in error-handler statement refs (fa1c909)
   • Rejoin empty custom error handler at IF's ELSE first activity (b351068)
   • Address merged microflow review followups (76e1989)
   • Allow expressions in add-to-list statements (6d7b92c)
   • Track add-to-list expression inputs (0f3fbe3)
   • Use valid add-to-list expression fixture (a0c3ef4)
   • Honor UseReturnVariable when emitting call-action assignments (1568e64)

9. SET Command and Session Variables:

   • SET format = json now takes effect for subsequent statements (d73e9c9) [fixes REPL: SET key = value listed in HELP but not implemented (scaffolding only) #471]
   • Implement session-level SET key = value command (96cecc3) [fixes REPL: SET key = value listed in HELP but not implemented (scaffolding only) #471]

10. Catalog and Associations:

    • Preserve cross-module associations on CREATE object actions (efeefea)
    • CATALOG.ASSOCIATIONS/CONSTANTS/OBJECTS returning no rows (issue CATALOG.ASSOCIATIONS table missing from catalog #419) (7a45dc2) [fixes CATALOG.ASSOCIATIONS table missing from catalog #419]

11. Merged Pull Requests (note: the commits show many merges, but the PRs section says no PRs merged in the last 24h? However, the commits include merge commits. We'll note that the PRs merged are reflected in the merge commits, but the "Pull Requests Merged" section says none. This might be because the digest is for the last 24h and the merges might have been done earlier? But the commits are from the last 24h. Let's check the data: the commits list includes merge commits (e.g., 74595ec, 5a5b743, etc.). However, the provided "Pull Requests Merged (last 24h)" says "No PRs merged.". This is inconsistent. We'll follow the provided data for the PRs section.

But note: the data says:

Pull Requests Merged (last 24h)

No PRs merged.

However, the commits include merge commits. This might be because the merge commits were made in the last 24h but the PRs were opened earlier? The digest is for the last 24h, so we should report what the data says.

Given the data, we'll stick to the provided sections.

Pull Requests

• Merged: none (as per data)
• Opened: none (as per data)
• Currently Open PRs:
  • fix: roundtrip REST mapping cardinality via as list of syntax #519: fix: infer SingleObject from import mapping root when JsonStructure absent
  • fix: always emit merge for continuing inheritance split branches (CE0079) #475: fix: always emit merge for continuing inheritance split branches (CE0079)
  • docs: add manual test case documentation for all MDL command areas #386: docs: add manual test case documentation for all MDL command areas
  • feat: support inheritance split and cast statements #365: feat: support inheritance split and cast statements
  • feat: add modelsdk — auto-generated type-safe model SDK #335: feat: add modelsdk — auto-generated type-safe model SDK

Issues

• Opened (last 24h):
  • Compiler-enforced backend boundary between executor and sdk/mpr #518, Code-generate the backend mock to eliminate manual sync #517, Command self-registration in executor to reduce agentic discovery cost #516, Split MDLParser.g4 by domain to reduce grammar merge conflicts #515, Remove generated ANTLR parser files from git #514, feat: mxcli scaffold crud — generate standard CRUD pages, microflows, and navigation from an entity #513, feat: mxcli exec --dry-run — preview changes without applying #512, fix: SET $obj/Module.Assoc = $other rejected — isVariableDeclared does not handle path-style targets #511, fix: standardise on CREATE OR MODIFY — remove/deprecate CREATE OR REPLACE variants #510, Microflow roundtrip: REST call with retry-loop error handler loses main-path variable scope (CE0108) #506 -> 10 issues
• Closed (last 24h):
  • fix: resolveSnippetRef ignores in-session cache, causing forward snippet references to fail #509, Daily Digest: 2026-05-04 #505, REPL: SET key = value listed in HELP but not implemented (scaffolding only) #471, GRANT with XPath WHERE clause produces empty access rules (permissions lost) #431, SIGSEGV in visitor_rest.go:386 on end resource syntax in CREATE PUBLISHED REST SERVICE #429, CATALOG.ASSOCIATIONS table missing from catalog #419, describeNanoflow loses void-microflow EndEvent fix #406, Reverse retrieve incorrectly classified when output feeds add/remove-from-list statements #405, Manual while-true detection over-triggers when continue lives only inside nested loop body #404, mxcli report hangs indefinitely after catalog load #397, Allow expressions in add-to-list microflow statements #361, Add module dump command for bulk export #130, DESCRIBE PAGE widget names don't match ALTER PAGE identifiers #116, Use import and export mappings in rest calls #102 -> 14 issues
• Total open issues: the repo stats say 1 open issue, but note that the issues opened and closed are for the last 24h. The total open issues is given in the repo stats as 1.

However, note that the issues opened in the last 24h (10) and closed in the last 24h (14) would change the total open issues. But the repo stats section says "Open issues: 1". This is likely the current total at the time of the digest.

We'll use the repo stats for the total open issues.

Repository Health

• Stars: 77
• Forks: 25
• CI Status:
  • Daily Project Digest: [2026-05-05T09:04:30Z] (we don't have the status, but the other two are success)
  • Build, Test & Lint: success
  • Push on main: success

So CI is passing.

Action Items

We need to look for anything that needs attention: failing CI, stale PRs, unanswered issues.

• CI: all success -> no failing CI.
• Stale PRs: we have open PRs, but we don't have ages. However, note that PR feat: add modelsdk — auto-generated type-safe model SDK #335 is from a long time ago (likely stale) and feat: support inheritance split and cast statements #365, docs: add manual test case documentation for all MDL command areas #386, fix: always emit merge for continuing inheritance split branches (CE0079) #475, fix: roundtrip REST mapping cardinality via as list of syntax #519 are more recent? Without dates, we can only note the open PRs and suggest checking for staleness.
• Unanswered issues: the issues opened in the last 24h are new and may not have been answered yet.

But note: the issues opened in the last 24h are 10, and they are all from @ako (the same user) and seem to be feature requests and fixes. They might be part of a planning session.

Given the digest is daily, we can note:

• There are 10 new issues opened in the last 24h (which is a lot) and they are all feature requests or fixes. This might indicate a planning burst, but we should check if they are being addressed.

However, the action items section should be concise. We can note:

• The high number of new issues (10) opened in the last 24h may require triage.
• Check the oldest open PRs for staleness (especially feat: add modelsdk — auto-generated type-safe model SDK #335 which is about adding modelsdk and has been open for a while).

But note: the repo stats say only 1 open issue total? That doesn't match with the 10 opened and 14 closed in the last 24h. This suggests that the repo stats might be outdated or the digest is showing a snapshot. We'll trust the repo stats for the total open issues (1) and note that the last 24h saw 10 opened and 14 closed, so the net change is -4, leading to a total of 1 (if we assume the total was 5 before the last 24h: 5 + 10 - 14 = 1).

So the repository is healthy in terms of issue resolution.

Now, let's structure the response.

Highlights (1-3 bullet points):

• Released v0.8.0 with various fixes and features.
• Fixed macOS-specific issues (test isolation and exec format error) to improve reliability on Apple systems.
• Resolved multiple bugs including snippet reference caching, SET command implementation, and catalog associations.

Code Changes (summarize by theme):

• Parser refactoring: Split MDLParser.g4 into domain-specific files to reduce merge conflicts.
• Release and versioning: Released v0.8.0 and updated Mendix version support.
• macOS fixes: Made Applications directory mockable and fixed Studio Pro lookup error.
• Snippet and session handling: Enhanced resolveSnippetRef to use session cache and implemented session-level SET commands.
• JSON structure improvements: Fixed qualified-name lookup through folder hierarchy and added regression tests.
• Microflow and error handler fixes: Addressed issues with add-to-list expressions, error handler rejoin, and variable scoping.
• Catalog and associations: Fixed cross-module association preservation and catalog table queries.
• VS Code extension: Extended LSP to

---

Daily digest generated automatically — workflow source