Daily Digest: 2026-06-11

[github-actions]

We are given a daily digest for 2026-06-11. 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 (as of the digest):

• Stars: 91
• Forks: 32
• Watchers: 6
• Open issues: 1 (but note: we have issues opened and closed in the last 24h, so we'll compute the current open issues from the data)

Commits (last 24h): 20 commits, all by Andrej Koelewijn.

Pull Requests Merged (last 24h): None.

Pull Requests Opened (last 24h): None.

Currently Open PRs:

• deps: bump vscode-languageclient from 9.0.1 to 10.0.0 in /vscode-mdl #646 (dependabot: bump vscode-languageclient)
• fix #590: rewrite OData example Level 9.1 to use TripPin schema actions #592 (fix 10-odata-examples.mdl Level 9.1 crashes Studio Pro project check (NRE in CallExternalAction.SchemaAction) #590: rewrite OData example)
• docs: add manual test case documentation for all MDL command areas #386 (docs: add manual test case documentation)

Issues Opened (last 24h):

• Catalog: residual objects-view members + mod-time staleness follow-ons (index completeness & large-project build done) #658: Catalog: residual objects-view members + mod-time staleness follow-ons
• ALTER ENTITY ADD ATTRIBUTE drops system members (createdDate) on sibling generalization root — CE1613 across inheriting entities #657: ALTER ENTITY ADD ATTRIBUTE drops system members (createdDate) on sibling generalization root
• Java action writer emits legacy MicroflowActionInfo with null ImageData, crashing Studio Pro export/upgrade #656: Java action writer emits legacy MicroflowActionInfo with null ImageData

Issues Closed (last 24h):

• Daily Digest: 2026-06-10 #655: Daily Digest: 2026-06-10
• REFRESH CATALOG SOURCE leading to timeout (5mins) #651: REFRESH CATALOG SOURCE leading to timeout (5mins)

CI Status (latest runs on main):

• Daily Project Digest [2026-06-11T11:18:41Z] (this is the digest generation, so we can ignore for health? but note it's a run)
• success — Build, Test & Lint [2026-06-11T10:57:56Z]
• success — Push on main [2026-06-11T10:42:44Z]

Dependency Changes: None.

Now, let's structure the response:

1. Highlights: We need 1-3 bullet points of the most important changes.

   • Looking at the commits, there is a lot of work on MCP (Mendix Capability Protocol) and catalog improvements.
   • Notable:
     • feat(mcp): version-keyed capability registry + Capabilities model (ADR-0004 slice 2) [2917a8f]
     • feat(mcp): mxcli mcp capabilities — agent-facing capability report (ADR-0004 slice 1) [744d6dc]
     • docs(adr): ADR-0004 version-aware MCP capability model + proposal build plan [006e874]
   • Also, significant work on workflows (CREATE/ALTER WORKFLOW, etc.) and catalog indexing (various schema versions).
   • However, for highlights, we can pick the overarching theme: ADR-0004 (MCP capability model) and workflow enhancements.

   Let's choose:

   • Major progress on ADR-0004: version-keyed capability registry and agent-facing capability report.
   • Enhanced workflow support: CREATE/ALTER/DROP WORKFLOW with nested operations and property rewrites.
   • Catalog improvements: O(1) unit name lookups, indexing of various document types (image collections, JS actions, etc.), and associations.

2. Code Changes: Summarize by theme.

   • MCP (Mendix Capability Protocol):
     • Version-keyed capability registry and Capabilities model (ADR-0004 slice 2)
     • Agent-facing capability report (mxcli mcp capabilities) (ADR-0004 slice 1)
     • Workflow enhancements: CREATE/ALTER/DROP WORKFLOW (with nested activities, boundary events, etc.), CREATE MICROFLOW, CONSTANT support, rejection of unsupported operations (NANOFLOW, JAVA ACTION) with clear reasons.
     • Document creation into folders (folder clause) for MCP.
   • Catalog:
     • Indexing improvements: image collections, JS actions, data transformers (schema v4), agent-editor documents (schema v5), associations (schema v3)
     • Performance: O(1) unit name lookups and source-build progress
     • Fixes: SHOW CATALOG TABLES listing every catalog view, trusting fresh catalog for auto-detect type
   • MDL (Mendix Definition Language):
     • Bare describe Module.Name auto-detects type in MDL grammar
     • Auto-detect document type from qualified name in describe
   • Documentation:
     • ADR-0004 documentation
     • MCP/PED backend architecture and mutation-constraint model (wiki)
     • Backend-coverage matrix added to MDL_FEATURE_MATRIX
     • Note on generating backend-coverage MCP column as follow-up
   • Other:
     • Fix init: install Podman via Dockerfile (not non-existent feature)

3. Pull Requests:

   • Merged (last 24h): None.
   • Opened (last 24h): None.
   • Pending review (currently open): 3 PRs (deps: bump vscode-languageclient from 9.0.1 to 10.0.0 in /vscode-mdl #646, fix #590: rewrite OData example Level 9.1 to use TripPin schema actions #592, docs: add manual test case documentation for all MDL command areas #386)

4. Issues:

   • New (last 24h): 3 (Catalog: residual objects-view members + mod-time staleness follow-ons (index completeness & large-project build done) #658, ALTER ENTITY ADD ATTRIBUTE drops system members (createdDate) on sibling generalization root — CE1613 across inheriting entities #657, Java action writer emits legacy MicroflowActionInfo with null ImageData, crashing Studio Pro export/upgrade #656)

   • Closed (last 24h): 2 (Daily Digest: 2026-06-10 #655, REFRESH CATALOG SOURCE leading to timeout (5mins) #651)

   • Total open: We are told in the repository stats that open issues are 1, but note that the stats might be as of the time of the digest generation. However, we have:

     • Previously open issues: we don't have the exact number, but we know from the stats that open issues were 1 (as per the table).
     • Then we opened 3 and closed 2, so the new total open would be: 1 (previous) + 3 - 2 = 2.
       However, the repository stats table says "Open issues: 1". This might be a discrepancy. But note: the digest is generated at a specific time, and the stats might be from the beginning of the day?
       Since the instructions say to use the provided data, we'll note:
     • The repository stats table says open issues: 1 (but we see 3 new and 2 closed, so it doesn't add up).
       Alternatively, the stats might be updated after the digest?
       Let's stick to the data we have:
     • We are told in the repo stats: open issues = 1.
     • But we also see 3 new issues and 2 closed in the last 24h.
       This suggests that the repo stats might be from before the last 24h?
       However, the digest is for 2026-06-11, and the stats are provided as part of the digest.
       We'll report the issues as:
     • New: 3
     • Closed: 2
     • Total open: We don't have a direct number, but the repo stats say 1. However, note that the digest generation might have changed the count?
       Since the digest issue Daily Digest: 2026-06-10 #655 was closed (which is the digest for 2026-06-10), and we are generating the digest for 2026-06-11, it's likely that the open issues count in the stats is after the events of the last 24h?
       But wait: the stats table is provided at the top, and then we have the commits, PRs, issues.
       The stats table says open issues: 1.
       Then we see 3 new issues and 2 closed.
       If the stats table is current, then the open issues should be: previous open + 3 - 2 = 1 -> so previous open must have been 0?
       But that doesn't match because we closed Daily Digest: 2026-06-10 #655 (which was open) and REFRESH CATALOG SOURCE leading to timeout (5mins) #651 (which was open).
       Alternatively, the stats table might be outdated?
       Given the confusion, we'll report:
     • New issues: 3
     • Closed issues: 2
     • And note that the repository stats indicate 1 open issue (which may be the current state after the last 24h?).

     However, the digest generation process might have updated the stats?
     Since we are generating the digest, and the stats are provided, we'll use the stats for the total open: 1.

     But note: the digest for 2026-06-10 (Daily Digest: 2026-06-10 #655) was closed today, so that issue is no longer open.
     And REFRESH CATALOG SOURCE leading to timeout (5mins) #651 was closed today.
     So if there was 1 open issue at the start of the day, and we closed 2 and opened 3, then we would have 1 - 2 + 3 = 2 open issues.
     But the stats say 1.

     Let's reexamine the stats table: it says "Open issues: 1".
     And then in the issues closed we see Daily Digest: 2026-06-10 #655 and REFRESH CATALOG SOURCE leading to timeout (5mins) #651.
     So if Daily Digest: 2026-06-10 #655 and REFRESH CATALOG SOURCE leading to timeout (5mins) #651 were two of the open issues, then closing them would reduce the count by 2.
     But we also opened 3.
     So if the count was X at the start of the day, then: X - 2 + 3 = X+1 = 1 (from the stats) -> X=0.
     That would mean at the start of the day there were 0 open issues, then we opened 3 and closed 2, leaving 1.
     That matches the stats.

     Therefore, we can say:

     • Total open issues: 1 (as per the repository stats)

5. Repository Health:

   • Stars: 91
   • Forks: 32
   • CI status:
     • The latest runs on main show two successes (Build, Test & Lint and Push on main) and one run for the digest (which we can ignore for health as it's a documentation task).
     • So CI is passing.

6. Action Items:

   • We have 3 open PRs:
     • deps: bump vscode-languageclient from 9.0.1 to 10.0.0 in /vscode-mdl #646: dependabot bump (vscode-languageclient) - this is automated, but we should check if it's been reviewed? It's been open for a while (since deps: bump vscode-languageclient from 9.0.1 to 10.0.0 in /vscode-mdl #646 is the oldest? we don't have dates, but the PR numbers are increasing so docs: add manual test case documentation for all MDL command areas #386 is the oldest).
     • fix #590: rewrite OData example Level 9.1 to use TripPin schema actions #592: fix 10-odata-examples.mdl Level 9.1 crashes Studio Pro project check (NRE in CallExternalAction.SchemaAction) #590 (OData example) - opened by ako.
     • docs: add manual test case documentation for all MDL command areas #386: docs: add manual test case documentation - opened by retran (looks like an external contributor?).
   • We should check if any of these PRs are stale or need attention.
     • Without dates, we can't tell how long they've been open, but note that the digest is daily and we are only seeing the last 24h for activity.
     • However, the fact that they are still open and no new PRs were opened in the last 24h suggests they might be waiting for review.
   • Also, we have 3 new issues opened in the last 24h that need attention.
   • CI is passing, so no failing CI.

   Action items:
   - Review and merge the open PRs (especially docs: add manual test case documentation for all MDL command areas #386 which is documentation and might be straightforward).
   - Triage the new issues (Java action writer emits legacy MicroflowActionInfo with null ImageData, crashing Studio Pro export/upgrade #656, ALTER ENTITY ADD ATTRIBUTE drops system members (createdDate) on sibling generalization root — CE1613 across inheriting entities #657, Catalog: residual objects-view members + mod-time staleness follow-ons (index completeness & large-project build done) #658).

Now, let's write the digest in markdown.

Note: We must be concise.

Highlights:

• Major progress on ADR-0004: implemented version-keyed capability registry and agent-facing capability report (mxcli mcp capabilities).
• Enhanced workflow support: added CREATE/ALTER/DROP WORKFLOW with nested operations, property rewrites, and support for various workflow elements (call-workflow, wait-for-notification, etc.).
• Catalog improvements: O(1) unit name lookups, indexing of image collections, JS actions, data transformers, agent-editor documents, and associations; plus fixes for catalog staleness and view listing.

Code Changes:

• MCP: Capability model (ADR-0004), workflow enhancements (CREATE/ALTER/DROP, nested activities, CONSTANT, MICROFLOW), document creation in folders, rejection of unsupported operations (NANOFLOW, JAVA ACTION) with clear reasons.
• Catalog: Schema-based indexing (v3: associations, v4: image collections/JS actions/data transformers, v5: agent-editor documents), O(1) unit lookups, performance improvements, fixes for SHOW CATALOG TABLES and auto-detect type.
• MDL: Auto-detection of document type for bare describe Module.Name and qualified names.
• Documentation: AD

---

Daily digest generated automatically — workflow source