Daily Digest: 2026-04-30

[github-actions]

We are given a daily digest for 2026-04-30. 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: 75
• Forks: 23
• Watchers: 6
• Open issues: 1 (but note: the issues opened in the last 24h are many, and we have a list of closed issues too. The open issues count in the stats is 1, but we see many issues opened in the last 24h. However, note that the stats say "Open issues: 1" at the top, but then we have a list of issues opened (last 24h) and closed (last 24h). We must reconcile: the open issues count in the stats is the current total open issues. The issues opened in the last 24h are new, and the closed ones are resolved. We'll use the stats for the current open issues count.

Commits (last 24h)

There are many commits (about 30). We need to summarize by theme.

Looking at the commits, we see:

• Many fixes related to nanoflows (by Andrew Vasilyev):
  • nanoflow validation, lookup, body checks
  • omitting empty JS/Java action params
  • resolving unparseable nanoflows (negative literals, XPath, etc.)
  • LSP snippet completions for nanoflow statements
  • addressing PR review (denylist, cache, mocks/docs)
  • ELK diagram test cases, propagating ELK errors, dedup entity lookup
  • nanoflow ELK diagram support for VS Code preview
  • nanoflow BSON mapping, Go example, test cases, validation fixes
  • call javascript action MDL pipeline and association retrieve fix
  • rewriting nanoflow test cases as QA manual test documentation
  • error propagation, MDL output fields, isNumericLiteral hardening
  • adding nanoflow references across documentation
  • adding SHOW ACCESS, MERMAID, diff, and describe improvements
  • adding CALL NANOFLOW, GRANT/REVOKE nanoflow access, agentic skill, proposal
  • adding CREATE/DROP NANOFLOW support
• Fixes by Andrej Koelewijn:
  • remove duplicate previousStmtAnchor field in flowBuilder
  • use Forms$SnippetParameterMapping for snippet call parameter mappings
  • SHOW_PAGE button actions no longer produce null PageParameterMapping.Variable
• Other merges (by Ako) that are merging pull requests (which we'll see in the PRs section, but note: the PRs merged section says none, but these are merges of PRs? Actually, the commits include merge commits for PRs that were merged in the last 24h? However, the PRs merged section says "No PRs merged." but we see merge commits. This might be because the PRs were merged earlier and the merge commit is just now appearing? Or the PRs merged section is only for PRs that were merged and have a merge commit in the last 24h? But the data says no PRs merged. Let's note: the commits include merge commits (e.g., 6dc86b0 is a merge of PR feat: support free microflow annotations #319, a07e7e0 is a merge of PR fix(writer): drop synthetic trailing newline from EndEvent ReturnValue #317, etc.). However, the PRs merged section says none. This might be an inconsistency in the data. We'll follow the data: the PRs merged section says none, so we'll report that.

But note: the commit messages for merges say "Merge pull request #...", so they are merging PRs. However, the PRs merged section says none. We must rely on the provided data for the PRs merged section.

Pull Requests Merged (last 24h): None

Pull Requests Opened (last 24h): None

Currently Open PRs: a long list (from #408 down to #298)

Issues Opened (last 24h): many (from #409 down to #387, and note #400 and #398-#392 are also listed, but note the numbering: #409, #407, #406, #405, #404, #403, #402, #401, #400, #399, #398, #397, #396, #395, #394, #393, #392, #391, #390, #389, #388, #387) -> that's 23 issues opened in the last 24h.

Issues Closed (last 24h):

• Object-valued owner-both reverse retrieves can rebuild as lists #383, Daily Digest: 2026-04-29 #382, Reverse Reference retrieve with owner-both association is typed as single object #380, Writer emits invalid ChangeActionItem list markers for object changes #373, Preserve void EndEvent returns during microflow describe #368, Daily Digest: 2026-04-27 #353, Preserve manual while-true retry-loop roundtrips #350, MDL cannot distinguish free microflow notes from activity-bound annotations #318, MPR writer appends a synthetic newline to microflow EndEvent return values #316, Daily Digest: 2026-04-26 #303 -> 10 issues closed.

CI Status (latest runs on main):

• Daily Project Digest: success (2026-04-30T09:08:17Z)
• Enhancement Guide: skipped
• AI Issue Review: success

Now, let's structure the digest:

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

From the commits, we see a lot of work on nanoflows (by Andrew Vasilyev) and some fixes by Andrej Koelewijn. Also, note that there are many issues opened (23) and closed (10) in the last 24h, and a lot of open PRs (about 20+). However, the highlights should be about the most important changes in the code.

Given the volume of nanoflow-related commits, we can highlight:

• Significant progress on nanoflow support: validation, ELK diagram support, CREATE/DROP NANOFLOW, CALL NANOFLOW, etc.
• Fixes for microflow roundtrip issues (by Andrej Koelewijn and others) such as duplicate fields, snippet parameter mappings, and SHOW_PAGE button actions.

But note: the issues opened are mostly about various bugs and feature requests (many by @retran and @hjotha). The closed issues include some fixes.

We'll pick:

• Nanoflow implementation advances: added support for CREATE/DROP NANOFLOW, CALL NANOFLOW, GRANT/REVOKE nanoflow access, and ELK diagram support for VS Code preview.
• Fixes for microflow roundtrip: resolved issues with duplicate fields, snippet parameter mappings, and SHOW_PAGE button actions producing null mappings.
• High volume of issue activity: 23 new issues opened and 10 closed in the last 24h, indicating active development and bug hunting.

Code Changes: Summarize commits by theme.

Themes:

1. Nanoflow Enhancements and Fixes (Andrew Vasilyev):

   • Added validation parity, fast-path lookup, and consolidated flow body checks.
   • Fixed emission of empty JS/Java action params (omitting instead of invalid placeholder).
   • Resolved 5 unparseable nanoflows (negative literals, XPath predicates, embedded JSON, if-in-loop).
   • Added LSP snippet completions for nanoflow statements.
   • Addressed PR review: denylisted DownloadFileStmt, cached flow lookups, improved mocks/docs.
   • Added ELK diagram test cases, propagated ELK errors, deduplicated entity lookup, corrected docs.
   • Added nanoflow ELK diagram support for VS Code preview.
   • Added nanoflow BSON mapping, Go example, test cases, and validation fixes.
   • Added call javascript action MDL pipeline and fixed association retrieve.
   • Rewrote nanoflow test cases as QA manual test documentation.
   • Fixed error propagation, MDL output fields, and hardened isNumericLiteral.
   • Added nanoflow references across repository documentation.
   • Added SHOW ACCESS, MERMAID, diff, and describe improvements.
   • Added CALL NANOFLOW, GRANT/REVOKE nanoflow access, agentic skill, and proposal.
   • Added CREATE/DROP NANOFLOW support (grammar, AST, visitor, executor).

2. Microflow Fixes (Andrej Koelewijn and others):

   • Removed duplicate previousStmtAnchor field in flowBuilder.
   • Used Forms$SnippetParameterMapping for snippet call parameter mappings.
   • Fixed SHOW_PAGE button actions to no longer produce null PageParameterMapping.Variable.

3. Merge Commits (Ako):

   • Merged several pull requests (though the PRs merged section says none, we see merge commits for PRs feat: support free microflow annotations #319, fix(writer): drop synthetic trailing newline from EndEvent ReturnValue #317, feat: full nanoflow support — CREATE, DROP, SHOW, DESCRIBE, DIFF, MERMAID, security, and agentic skill #301, fix: preserve manual while-true loop roundtrips #354, fix: register import mapping result variable types #360, fix: infer java action result variable types #357, etc.) but note: these might be merges of older PRs? We'll note that there were merge commits but no new PRs merged in the last 24h (according to the PRs merged section).

Pull Requests:

• Merged: None (last 24h)
• Opened: None (last 24h)
• Currently Open: 20+ PRs (list provided, from fix: address merged microflow review followups #408 to Fix DESCRIBE PAGE / ALTER PAGE column name mismatch for DataGrid2 columns (#116) #298). We don't need to list them all, just note the count and that they are open.

Issues:

• New (last 24h): 23 issues opened (as listed, from Track remaining non-blocking follow-ups from merged PR reviews #409 to Developer Experience Report — Building a Full MVP via AI Agent #387, note: DESCRIBE ODATA SERVICE output not parseable — roundtrip broken #400 and mxcli fmt outputs to stdout instead of in-place, ignores invalid input #398-Unknown attribute type silently interpreted as enumeration reference #392 are included, but note the list has Track remaining non-blocking follow-ups from merged PR reviews #409, Add 'refresh' modifier to MDL change-object syntax (parity with commit/rollback) #407, 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, CREATE WORKFLOW with user task panics — nil pointer dereference #403, ALTER SNIPPET looks up page namespace instead of snippet namespace #402, CREATE PUBLISHED REST SERVICE allows duplicate qualified names #401, DESCRIBE ODATA SERVICE output not parseable — roundtrip broken #400, GRANT ... ON entity accepts non-existent module roles #399, mxcli fmt outputs to stdout instead of in-place, ignores invalid input #398, mxcli report hangs indefinitely after catalog load #397, SHOW CONTEXT OF <Entity> produces empty definition section #396, CREATE MICROFLOW accepts calls to non-existent microflows without error #395, DESCRIBE ENUMERATION emits unescaped single quotes in captions #394, DESCRIBE ENUMERATION drops documentation comments #393, Unknown attribute type silently interpreted as enumeration reference #392, DROP ENUMERATION with ambiguous unqualified name silently drops one #391, CREATE ENUMERATION accepts duplicate value names #390, CREATE ASSOCIATION allows duplicate qualified names #389, DESCRIBE ASSOCIATION emits DELETE_CASCADE but parser only accepts CASCADE #388, Developer Experience Report — Building a Full MVP via AI Agent #387 -> 23)
• Closed (last 24h): 10 issues (as listed: Object-valued owner-both reverse retrieves can rebuild as lists #383, Daily Digest: 2026-04-29 #382, Reverse Reference retrieve with owner-both association is typed as single object #380, Writer emits invalid ChangeActionItem list markers for object changes #373, Preserve void EndEvent returns during microflow describe #368, Daily Digest: 2026-04-27 #353, Preserve manual while-true retry-loop roundtrips #350, MDL cannot distinguish free microflow notes from activity-bound annotations #318, MPR writer appends a synthetic newline to microflow EndEvent return values #316, Daily Digest: 2026-04-26 #303)
• Total Open: According to the repository stats, there is 1 open issue. However, note that the stats might be outdated? But we must use the provided stats. The stats say "Open issues: 1". But we see 23 new issues opened and 10 closed in the last 24h. If we started with X open issues, then after 24h: X + 23 - 10 = X + 13. The stats say 1. This implies that before the last 24h, there were -12 open issues? That doesn't make sense.

Let me reexamine: the repository stats table says:

Metric	Count
Stars	75
Forks	23
Watchers	6
Open issues	1

This is the current state. Then we have:

• Issues Opened (last 24h): 23
• Issues Closed (last 24h): 10

So, if the current open issues are 1, then the number of open issues 24 hours ago was: 1 - 23 + 10 = -12? That is impossible.

Alternatively, the stats might be from a different time? Or the "Open issues" in the stats is the total open issues at the time of the digest, and the issues opened/closed in the last 24h are relative to that.

But note: the digest is for 2026-04-30. The stats are given at the top. The issues opened and closed in the last 24h are for the period leading up to this digest.

We must trust the stats: currently, there is 1 open issue. However, the list of issues opened in the last 24h includes 23 new issues, and closed includes 10. This would mean that 13 of the newly opened issues have already been closed? But the closed issues list only has 10, and they are specific issue numbers.

Alternatively, the stats might be wrong? But we are to use the data provided.

Given the confusion, we'll report:

• New issues (last 24h): 23
• Closed issues (last 24h): 10
• Total open issues: 1 (as per the repository stats)

But note: the issues opened list includes issues that are still open? And the closed list includes issues that were closed. The net change in open issues would be: +23 (opened) -10 (closed) = +13. So if the total open issues is now 1, then 24 hours ago there were 1 - 13 = -12? That doesn't make sense.

Wait, the repository stats

---

Daily digest generated automatically — workflow source