Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
109 commits
Select commit Hold shift + click to select a range
bebaaf4
feat(report): the scored report says whether the project builds
claude Nov 19, 2026
94cff14
Merge remote-tracking branch 'origin/main' into claude/gifted-fermi-2…
claude Nov 19, 2026
691d7ba
feat(verify): mxcli verify — one gate over check, lint and mx check, …
claude Nov 19, 2026
05253c8
Merge remote-tracking branch 'origin/main' into claude/verify-command
claude Nov 19, 2026
172c57d
fix(test): the list-marker census skips its optional submodule instea…
claude Nov 19, 2026
c8b14b8
fix(report): read the consistency check from mx check --json
claude Nov 19, 2026
04f63f5
Merge remote-tracking branch 'origin/main' into claude/gifted-fermi-2…
claude Nov 19, 2026
859c4d0
feat(report): report release says what a deploy does to production data
claude Nov 19, 2026
3a221ee
Merge pull request #2435 from ako/claude/gifted-fermi-2udffj
ako Nov 19, 2026
98eee80
Merge pull request #2434 from ako/claude/verify-command
ako Nov 19, 2026
6cb2c65
Merge remote-tracking branch 'origin/main' into claude/gifted-fermi-2…
claude Nov 19, 2026
956862f
Merge pull request #2436 from ako/claude/wonderful-edison-yxapt0
ako Nov 19, 2026
fdb6397
Merge branch 'mendixlabs:main' into main
ako Nov 19, 2026
cfc20dc
feat(verify): make verify the default gate in generated CLAUDE.md, bo…
claude Nov 19, 2026
92576dc
Merge remote-tracking branch 'origin/main' into claude/verify-default…
claude Nov 19, 2026
152c486
Merge remote-tracking branch 'origin/main' into claude/gifted-fermi-2…
claude Nov 19, 2026
406408f
Merge pull request #2437 from ako/claude/gifted-fermi-2udffj
ako Nov 19, 2026
866a075
Merge pull request #2438 from ako/claude/verify-default-gate
ako Nov 19, 2026
4e7d26d
feat(lint): MPR018 reports a model element named inside a string literal
claude Nov 19, 2026
384ce32
Merge remote-tracking branch 'origin/main' into claude/wonderful-edis…
claude Nov 19, 2026
a50a23e
feat(report): report dependencies — release line, Marketplace modules…
claude Nov 19, 2026
3e047c0
style: gofmt deps_collect_test.go
claude Nov 19, 2026
e827e36
Merge pull request #2441 from ako/claude/gifted-fermi-2udffj
ako Nov 19, 2026
9f4e446
Merge pull request #2440 from ako/claude/wonderful-edison-yxapt0
ako Nov 19, 2026
31ddcd5
feat(verify): list only gate-failing findings in text output; scope t…
claude Nov 19, 2026
3cabfc0
fix(report): a performance step counts its own requests, not backgrou…
claude Nov 19, 2026
70a5e9a
feat(report): one shared look for every report page, the scored repor…
claude Nov 19, 2026
6342e03
feat(report): report all writes every report into one folder with an …
claude Nov 19, 2026
8d8b948
feat(report): the scored page explains its number
claude Nov 19, 2026
5e81e5e
feat(report): tiles carry a status; traceability opens with an at-a-g…
claude Nov 19, 2026
422f44b
fix(report): an unused-document annotation may leave out the module
claude Nov 19, 2026
56eb1ca
fix(brain): brain list reports open questions as questions, not decis…
claude Nov 19, 2026
391904a
fix(report security): follow sub-microflows for caller checks and writes
claude Nov 19, 2026
cb3d7c7
feat(report security): the access grid shows create and delete apart …
claude Nov 19, 2026
7159cb9
feat(report security): callable flows grouped by what they take
claude Nov 19, 2026
b90598a
docs(report security): method and limits name the sub-microflow calle…
claude Nov 19, 2026
9ec9c5a
feat(report security): a settings and defaults section
claude Nov 19, 2026
4088ec8
feat(report tests): gaps by kind, startup and scheduled apart, what o…
claude Nov 19, 2026
11b3dc5
feat(report architecture): cohesion meters and cluster composition bars
claude Nov 19, 2026
b00039e
feat(report architecture): --exclude-docs leaves generated documents out
claude Nov 19, 2026
ff00d5a
fix(report security): judge sub-microflows on the entities a flow takes
claude Nov 19, 2026
1536723
feat(report tests): seed data apart from startup, gap names listed once
claude Nov 19, 2026
f837d02
docs(proposal): verify gate — how far one call goes (--apply, --throu…
claude Nov 19, 2026
de8123b
Merge pull request #2444 from ako/claude/gifted-fermi-2udffj
ako Nov 19, 2026
9d9c027
fix(catalog): a REST client's constant base URL is recorded
claude Nov 19, 2026
cc776ca
feat(catalog): published REST services record their authentication
claude Nov 19, 2026
478c523
feat(report): configuration — what each environment must supply
claude Nov 19, 2026
34bcaed
fix(report configuration): singular nouns in the lede
claude Nov 19, 2026
e1337c6
feat(report): readiness — one go/no-go page from the other reports
claude Nov 19, 2026
240095c
Merge pull request #2442 from ako/claude/verify-quiet-output
ako Nov 19, 2026
fea4ebf
Merge pull request #2445 from ako/claude/verify-proposal-apply
ako Nov 19, 2026
76ce7c3
style: gofmt readiness.go
claude Nov 19, 2026
5b424c8
feat(verify): --apply and --through, with an exec stage
claude Nov 19, 2026
619bce7
Merge pull request #2446 from ako/claude/gifted-fermi-2udffj
ako Nov 19, 2026
c789cc5
feat(report readiness): say which acceptances count, and explain the …
claude Nov 19, 2026
3682d90
fix(report all): hand each report its own inputs
claude Nov 19, 2026
0113ab0
fix(catalog): an incremental build leaves the catalog readable from e…
claude Nov 19, 2026
dd54f98
check: reject dropping an attribute, entity or association a document…
claude Nov 19, 2026
b6e66cf
fix(lint): a baseline records which rules ran, so a rule that did not…
claude Nov 19, 2026
46dce04
fix(report): span files may be gzipped
claude Nov 19, 2026
0f15032
fix(report): a missing test results file no longer fails the report
claude Nov 19, 2026
4cba104
feat(report): --local runs the tests without Docker
claude Nov 19, 2026
30c8850
fix(report readiness): a report that failed says so, not "not given"
claude Nov 19, 2026
5a4e94b
fix(lint): --update-baseline refuses while a rule cannot run; advice …
claude Nov 19, 2026
ebb9fab
feat(report all): --annotations-dir, and the overview names the annot…
claude Nov 19, 2026
3a201ec
docs(assess-quality): questions across reports with DuckDB
claude Nov 19, 2026
019c1d8
docs(assess-quality): fence the DuckDB queries as duckdb, not sql
claude Nov 20, 2026
81b35f3
Merge pull request #2447 from ako/claude/verify-apply
ako Nov 20, 2026
1254117
Merge pull request #2452 from ako/claude/gifted-fermi-2udffj
ako Nov 20, 2026
d51f000
Merge pull request #2457 from ako/claude/catalog-incremental-nested-r…
ako Nov 20, 2026
60c3a96
Merge origin/main into claude/lint-baseline-rules-ran
claude Nov 20, 2026
f885c74
Merge remote-tracking branch 'origin/main' into claude/lint-baseline-…
claude Nov 20, 2026
934e22d
feat(lint): MPR019 reports an XPath-filtered attribute with no leadin…
claude Nov 20, 2026
956169d
Merge remote-tracking branch 'origin/main' into claude/wonderful-edis…
claude Nov 20, 2026
4015666
Merge pull request #2458 from ako/claude/lint-baseline-rules-ran
ako Nov 20, 2026
7efedab
Merge pull request #2459 from ako/fix/2456-drop-member-references
ako Nov 20, 2026
e538c1e
fix(pages): write an empty progress message when a flow call has a pr…
claude Nov 20, 2026
6f2ab89
fix(microflows): a change or set error handler rejoins right after it…
claude Nov 20, 2026
d3c8d0e
catalog: resolve an attribute used through a document's own parameter…
claude Nov 20, 2026
d28707c
fix(javascript actions): store a Nanoflow parameter as Studio Pro doe…
claude Nov 20, 2026
265978c
fix(nanoflows): write, check and describe a JavaScript action's nanof…
claude Nov 20, 2026
afcea99
fix(check): type-check create/change member values and report a missi…
claude Nov 20, 2026
f6860b2
fix(check): run MDL044 over a call rest service's URL, headers, body …
claude Nov 20, 2026
24b3e79
fix(layouts): create layout takes folder:, and describe prints it
claude Nov 20, 2026
d9e7dbb
Merge origin/main
claude Nov 20, 2026
10b1c0d
verify: say the scripts were applied when a later stage fails (#2468)
claude Nov 20, 2026
21287b6
Merge pull request #2470 from ako/claude/issue-triage-prioritization-…
ako Nov 20, 2026
35cbb0e
Write Studio Pro's markers for ModuleSecurity.ModuleRoles and JS call…
claude Nov 20, 2026
c29188f
fix(init): the gate list follows the project's verify baselines, not …
claude Nov 20, 2026
d949af8
Merge pull request #2466 from ako/claude/wonderful-edison-yxapt0
ako Nov 20, 2026
babc790
Merge branch 'main' into fix/2468-catalog-variable-member-refs
ako Nov 20, 2026
4a123b4
Merge pull request #2469 from ako/fix/2468-catalog-variable-member-refs
ako Nov 20, 2026
beb577d
Merge branch 'main' into fix/2468-verify-apply-note
ako Nov 20, 2026
9f6ed9a
Merge pull request #2471 from ako/fix/2468-verify-apply-note
ako Nov 20, 2026
a5ff311
Merge remote-tracking branch 'origin/main' into claude/issue-triage-p…
claude Nov 20, 2026
78a494e
Merge pull request #2473 from ako/claude/issue-triage-prioritization-…
ako Nov 20, 2026
b97c48d
Merge pull request #2472 from ako/claude/gates-follow-baseline
ako Nov 20, 2026
4630fe2
feat(report performance): min–max per step, and steps grouped by finding
claude Nov 20, 2026
def69a5
feat(report traceability): one table of every requirement
claude Nov 20, 2026
f3a524b
Write every unit's keys in Studio Pro's order
claude Nov 20, 2026
c54fa37
feat(verify): say what the pre-existing findings are
claude Nov 20, 2026
f840223
Merge remote-tracking branch 'origin/main' into claude/issue-triage-p…
claude Nov 20, 2026
5e1ef91
fix(report): address the PizzaV1 review of #2475
claude Nov 20, 2026
8ad573f
Merge pull request #2480 from ako/claude/issue-triage-prioritization-…
ako Nov 20, 2026
c4ab2e7
mxcli new: say the first Studio Pro open may convert the project
claude Nov 20, 2026
1ad92fe
Merge pull request #2475 from ako/claude/gifted-fermi-2udffj
ako Nov 20, 2026
3ff2f02
Merge pull request #2479 from ako/claude/verify-open-counts
ako Nov 20, 2026
b949309
Merge remote-tracking branch 'origin/main' into claude/issue-triage-p…
claude Nov 20, 2026
fe8201f
Merge pull request #2483 from ako/claude/issue-triage-prioritization-…
ako Nov 20, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{"area": "cmd/mxcli/brain", "date": "2026-11-19", "symptom": "`brain list --json` reports open questions with kind \"decision\" (and `--kind decision` returns them), so a tool counting decisions counts every open question twice (ako/PizzaV1's overview had to filter `open: true` out by hand)", "cause": "List set each entry's kind with EntryKind(), which reads an open question as a decision; the stored form has no question kind", "file": "`cmd/mxcli/brain/list.go` (Store.List)", "insight": "Give the listing a reporting-only kind (KindQuestion) for open entries rather than a stored kind: EntryKind() keeps reading them as decisions for every internal consumer, and the JSON and --kind filter stop conflating them", "refs": ["ako/mxcli#2443"], "test": "TestListFiltersTheCommittedStore"}
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{"area": "cmd/mxcli", "date": "2026-11-19", "symptom": "report all --run in an environment where the tests cannot run: tests AND traceability 'Not generated: open out/junit.xml: no such file or directory', though --journeys/--spans were given", "cause": "collectEvidence recorded the failed `mxcli test` as a warning but then failed the whole report reading the results file the run never wrote", "file": "`cmd/mxcli/cmd_report_evidence.go` (collectEvidence)", "insight": "Evidence a report can stand without is a warning when it is missing, not an error: the error hid the real cause (the failed run) behind a file-not-found, and took the journeys down with it", "refs": ["ako/mxcli#2452"], "test": "TestMissingJUnitIsAWarningNotAFailure"}
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{"area": "cmd/mxcli", "date": "2026-11-19", "symptom": "`report performance` shows random steps several seconds slower than they are: on ako/PizzaV1 'place order and pay' read 4,884 ms of server time while its own requests took 280 ms", "cause": "spansIn gave a step every span that started inside its time window, so a queued task (the simulator's 1.5 s clock tick), scheduled events and the task queue's polling counted as the step's server time, database time and queries", "file": "`cmd/mxcli/projectreport/performance.go` (spanIndex.stepSpans)", "insight": "Attribute by trace, not by time: a step owns the traces rooted in an HTTP request to the app port (the most common server.port among http roots) that start in its window; other roots are background, measured apart. With that, db time matched the project's own analysis on all 12 steps. Keep the window rule only as a labelled fallback for collectors without http attributes", "refs": ["ako/mxcli#2443"], "test": "TestPerformanceCountsOnlyTheStepsOwnRequests"}
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{"area": "cmd/mxcli", "date": "2026-11-19", "symptom": "`mxcli report --format html` draws every score bar as an empty grey track, whatever the score (ako/PizzaV1 shipped tools/fix_quality_html.py to patch it)", "cause": "The linter's own HTML formatter gave .score-fill a width but no display rule, so the inline span ignored its width; the scored report also had a style of its own, apart from every report kind", "file": "`cmd/mxcli/projectreport/quality.go` (QualityDoc) and `doc.go` (.meter)", "insight": "Render the scored report's page through the shared Doc renderer instead of fixing the one-off CSS: one style to maintain, and the bar is a block element with a coloured fill. The renamed class (.meter) also avoids the software map's own .bar control rows, which a shared .bar rule squashed", "refs": ["ako/mxcli#2443"], "test": "TestQualityDocBarsHaveAFill"}
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{"area": "cmd/mxcli", "date": "2026-11-19", "symptom": "report all: traceability proves 5 of 111 requirements where report traceability proves 101, readiness can never pass 'not assessed in full' (no way to give test results), and performance shows one 'step' per functional journey, each over budget", "cause": "passThrough forwarded --journeys/--spans to performance and tests only, report all had no --junit/--run/--tests, and one journey log fed both the functional reports and performance", "file": "`cmd/mxcli/cmd_report_all.go` (passThrough, needsInput)", "insight": "A roll-up is only as right as the inputs it hands on: test it per receiving report (TestReportAllHandsEachReportItsOwnInputs), not only that every page is written. A functional log and a performance run are different evidence and get different flags; --run runs once and leaves junit.xml for the next report to read", "refs": ["ako/mxcli#2451"], "test": "TestReportAllHandsEachReportItsOwnInputs"}
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{"area": "cmd/mxcli", "date": "2026-11-19", "symptom": "the security report flags a callable flow high although its sub-microflows show it is not (Shop.DS_Info_Line on ako/PizzaV1: takes a Product, creates the caller's own cart line), and labels flows that commit the parameter's entity in a sub as reading only", "cause": "collectCallableFlows looked at the flow's own body only, and 'writes' meant any write to any entity; entity access off + any write was high whatever the parameter entity's read rule", "file": "`cmd/mxcli/projectreport/security.go` (collectCallableFlows, anyOnEntity)", "insight": "Follow the call closure, but judge it on the entities the flow takes: a sub that stamps [%CurrentUser%] on a Toast turned 19 PizzaV1 flows 'ok' in a first cut, and creating one's own cart line is not changing what the client chose. The client can only pass objects its role may read, so entity access off + a write is high only when the read rule is 'all'; otherwise the read rule bounds it (PizzaV1's hand review: 'only the guest's own rows'). Compare a new verdict rule against a hand-reviewed app before trusting it", "refs": ["ako/mxcli#2443"], "test": "TestCallableFlowFollowsSubMicroflows"}
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{"area": "cmd/mxcli", "date": "2026-11-19", "symptom": "--spans after-spans.jsonl.gz fails: \"line 1: invalid character '\\x1f' looking for beginning of value\"", "cause": "readSpanFile parsed the file's bytes as JSONL/OTLP without checking for gzip", "file": "`cmd/mxcli/projectreport/otlp.go` (readSpanFile)", "insight": "Decide on the gzip magic bytes (1f 8b), not the extension, then pick the format from the name without .gz — so a .pb.gz is still protobuf and a mis-named file still reads", "refs": ["ako/mxcli#2452"], "test": "TestReadSpansGzip"}
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{"area": "cmd/mxcli", "date": "2026-11-19", "symptom": "an architecture-report annotation `unused:FaultProbe` changes nothing; the document stays 'verify' and the key is listed under 'annotations that matched nothing' (ako/PizzaV1 had to rename every key to `unused:Shop.FaultProbe`)", "cause": "the page looked the key up by the qualified name only, while the unused table and the natural way to write the key both say just the document name", "file": "`cmd/mxcli/projectreport/architecture.go` (RenderArchitecture, unused table)", "insight": "Accept the short key only when the short name is unique among the unused documents; an ambiguous one stays visibly unmatched rather than annotating the wrong document", "refs": ["ako/mxcli#2443"], "test": "TestUnusedAnnotationWithoutModule"}
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{"area": "cmd/mxcli", "date": "2026-11-20", "symptom": "Making `verify` the gate in the generated CLAUDE.md (ako/mxcli#2438) was meant to reach new projects only. It reached every bootstrapped project: the session-start bootstrap runs `mxcli init --sync-skills .` each session, which regenerates the mxcli section of CLAUDE.md, so an upgraded mxcli replaced `lint` and `docker check` with `verify` in projects that had no verify-baseline/. Without baselines verify reports every finding the project already had as new, and a project with errors fails on its whole backlog.", "cause": "The gate list was a single package-level list chosen when mxcli was built, and the generator had no way to see the project: ToolFile.Content takes only the project name and the .mpr file name. I assumed init-time generation (the PR text and proposal question 12 said existing projects keep their old list) without reading what `--sync-skills` regenerates. The sync path (init_tooling_sync.go) re-renders owned docs from the same list on every session start.", "file": "`cmd/mxcli/init_claudemd.go` (classicGates, verifyGates, hasVerifyBaseline, projectGatesFor, generateClaudeMDIn), `cmd/mxcli/tool_templates.go` (ToolFile.ContentIn, render), `cmd/mxcli/init.go`, `init_tooling_sync.go`, `cmd_add_tool.go`; tests in `cmd/mxcli/init_claudemd_gates_test.go`.", "insight": "Before changing generated text that lives in a project's own files, find every path that regenerates it, not only the one that creates it: a sync that runs unattended every session turns a binary upgrade into a change of every project's instructions. The fix makes the generated list a function of the project (the verify gate list only when verify-baseline/lint.json exists), so recording the baselines moves a project onto verify at the next sync and an upgrade alone moves nothing. A test must exercise the sync path with and without the file (TestSyncMovesAProjectOnAndOffTheVerifyGateList), not only the generator, because the generator alone cannot show who calls it. Found by asking what the risk of the default was and then reading init --sync-skills; the ChipCoV14 clone's own .claude/bootstrap-mxcli.sh showed the call."}
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{"area": "cmd/mxcli", "date": "2026-11-20", "refs": ["ako/mxcli#2468", "ako/mxcli#2447"], "ce": [], "symptom": "`mxcli verify --apply` that passed check and exec and then failed mxcheck printed `Result: FAILED (exit 20)` exactly like a gate that wrote nothing, although exec had already written the project; the broken change stayed in the project until someone noticed.", "file": "cmd/mxcli/verify/render.go WriteText; test render_test.go TestWriteTextSaysTheScriptsWereAppliedWhenALaterStageFails; help text in cmd/mxcli/cmd_verify.go", "cause": "The text renderer printed the same Result line for every non-zero exit; Result.Applied (exec ran and wrote) was in the JSON but never read by the text output.", "insight": "**The signal already existed; the renderer ignored it.** Result.Applied was set when exec applied the scripts, so the fix reads it rather than adding state. The test needs three controls — a passing run, a run that never applied, and a check that failed before exec — because the sentence is only true when exec wrote AND something later failed; a stub of the condition fails exactly one test, the positive one."}
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{"area": "mdl/backend", "date": "2026-11-19", "symptom": "a consumed REST service whose base URL is a constant shows an empty BaseUrl in the catalog (CATALOG.CONSUMED_REST_SERVICES), indistinguishable from one with no base URL", "cause": "the reader type-asserted Rest$ValueTemplate only; a Rest$ConstantValue base URL fell through and was dropped", "file": "`mdl/backend/modelsdk/integration_read.go` (restBaseURL)", "insight": "A gen property typed element.Element is a union: read every concrete type it can hold, not the one the writer emits. Kept apart from BaseUrl (BaseUrlConstant) so describe and its round trip, which only know literals, are unchanged", "refs": ["ako/mxcli#2426"], "test": "TestRestBaseURLReadsTheConstant"}
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{"area": "mdl-backend", "date": "2026-11-20", "refs": ["ako/mxcli#2467", "ako/mxcli#258"], "ce": [], "symptom": "Studio Pro rewrote mxcli-made units on first open: an empty Security$ModuleSecurity.ModuleRoles stored with marker 1 and a Microflows$JavaScriptActionCallAction.ParameterMappings stored with marker 3, where Studio Pro writes 3 and 2. check, exec and mx check passed; only the git diff after opening showed it.", "file": "mdl/backend/modelsdk/module_write.go (ModuleSecurity TypeDefaults), mdl/backend/modelsdk/microflow_write.go (JavaScriptActionParameterMapping). Test: mdl/backend/modelsdk/list_markers_2467_test.go", "cause": "ModuleRoles was registered as marker 1 on the reading that it is a by-name role list; it holds the roles themselves. The JS mapping child type was never registered, so it fell back to the encoder default 3.", "insight": "**A list's marker follows what it holds, not what it is called**: ModuleRoles is 1 on UserRole (names) and 3 on ModuleSecurity (parts). Settle a marker with a census of a Studio Pro-made project (owner $Type.key -> marker counts), never by analogy. Register it per owner/key too, so canon.NormalizeListMarkers corrects the units an older mxcli already stored on their next write."}
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{"area": "mdl-backend", "date": "2026-11-20", "refs": ["ako/mxcli#2448", "mendixlabs/mxcli#1902"], "ce": [], "symptom": "`call microflow … with (ProgressBar: Blocking)` without ProgressMessage stored Forms$MicroflowSettings.ProgressMessage as null; check, exec and mx check passed, the project opened, and Studio Pro 10.24.28 crashed exporting the page (NullReferenceException in MicroflowSettings.WriteProperties) and errored on typing in the progress-message field.", "file": "mdl/backend/modelsdk/widget_write.go progressMessageFor (microflowSettingsToGen, CallNanoflowClientAction). Test: mdl/backend/modelsdk/progress_message_null_2448_test.go", "cause": "The writer set ProgressMessage only when the script gave one; RegisterTypeDefaults lists it under NullFields, which is right only for ProgressBar None.", "insight": "**Null is a valid default only for the value of the enum it belongs to.** The reporter's census of a real 10.24 project (None+null 210, Blocking+Text 22, NonBlocking+Text 11, Blocking+null 2 — both mxcli's, both crashing) is the evidence; MxBuild 11.12.6 --target=deploy built both shapes without error, so the crash lives in Studio Pro's export, which no headless check here reaches. Decide such a default from Studio Pro's stored data, not from what the checker accepts."}
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{"area": "mdl/executor", "date": "2026-11-19", "refs": ["ako/mxcli#2456", "ako/mxcli#1258"], "ce": ["CE1613", "CE0161"], "symptom": "`alter entity E drop attribute \"A\"`, `drop entity E` and `drop association X` passed `check` (with or without --references) when a microflow, nanoflow, page or snippet still used the target; `exec` applied the drop with at most a \"may still reference\" warning (`drop entity` printed nothing) and `mx check` then reported CE1613 on each user (CE0161 where the attribute was only in an XPath).", "file": "mdl/executor/validate_dropped_member_references.go CheckDroppedMemberReferences (MDL108), called from cmd/mxcli/cmd_check.go in the catalog-backed tier. Tests: validate_dropped_member_references_test.go", "cause": "CheckEntityMemberDrops (MDL087) only reports members a `create or modify` loses without being asked; an explicit drop is excluded by intent, and nothing asked who else uses the dropped member. The catalog already holds the answer (`show references to`).", "insight": "**The reference graph is the whole rule; the work is deciding what NOT to report.** Measured one project per case on MxBuild 11.16.1: microflow, nanoflow, page and snippet users are CE1613, an XPath-only user is CE0161, dropping an entity that only an association points at is clean (the association goes with it), and dropping then re-adding the attribute is clean. So the rule reads only those four source types, ignores documents the script itself drops, creates or alters (it may fix the reference), skips a member the script puts back, and opens the FULL catalog (references are not in fast mode) only when the script has such a drop. `exec` still applies the drop: the project tier is check-only, like MDL087, so refusing there is a separate decision."}
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{"area": "mdl-executor", "date": "2026-11-20", "refs": ["ako/mxcli#2421", "mendixlabs/mxcli#1898"], "ce": [], "symptom": "In `change $Order … on error without rollback begin … end error; set $N = $N + 10; commit $Order on error …`, the change's handler rejoined at the commit handler's merge AFTER the commit, so at runtime an error in the change skipped the set and the commit. check, exec and mx check reported nothing; describe showed one shared `join rejoin1`.", "file": "mdl/executor/cmd_microflows_builder_actions.go addChangeObjectAction / addChangeVariableAction / addReplaceListAction pass no skip variable to finishCustomErrorHandler. Test: mdl/executor/error_handler_rejoin_change_2421_test.go", "cause": "finishCustomErrorHandler's skip variable defers a handler's rejoin until no later statement references it — right for an activity that CREATES the variable (it does not exist on the error path), but change/set/replace passed the variable they MODIFY, which exists on both paths, so every later use of $Order pushed the rejoin further down.", "insight": "**A 'skip' variable must be one the activity produces, not one it touches.** The skip exists so a handler does not rejoin before statements that need an object the failed activity never made; passing a pre-existing variable turns that into 'skip every later statement that mentions it'. Measured on 11.12.6: ChangeSetCommit and a three-change chain each rejoin right after their own activity; mx check 0 errors. `create` keeps the skip (control test)."}
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{"area": "mdl-executor", "date": "2026-11-20", "refs": ["ako/mxcli#2460", "mendixlabs/mxcli#1905"], "ce": [], "symptom": "`create layout M.L (layouttype: 'Responsive', folder: 'Layouts')` passed check, and exec refused it: 'unknown property \"folder\"'.", "file": "mdl/executor/cmd_pages_layout_v3.go buildLayoutV3 (Folder via pb.resolveFolder) and the rewrite path (applyDocumentFolder when the header names a folder); mdl/executor/cmd_pages_describe.go describeLayout prints folder:. Test: mdl/executor/layout_folder_2460_test.go", "cause": "The layout header's allow-list (added to stop silently ignored properties) did not include folder, which pages and snippets take; check does not run the builder, so only exec saw the refusal; and describe never printed a layout's folder, so a round trip would have moved a foldered layout to the module root.", "insight": "**An allow-list that refuses unknown properties has to list every property its siblings accept, and check must agree with it.** Measured on 11.12.6: created in Layouts/Web, describe prints folder:, describe → exec Unchanged, a changed folder moves the layout, mx check 0 errors."}
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{"area": "mdl-executor", "date": "2026-11-20", "refs": ["ako/mxcli#2450", "mendixlabs/mxcli#1904"], "ce": ["CE0115", "CE0117"], "symptom": "`call javascript action … (callback = Module.Flow, other = empty)` for Nanoflow-typed parameters was written as Microflows$BasicCodeActionParameterValue with the name as expression: check and exec passed, mx check CE0115/CE0117. describe left Nanoflows$NanoflowParameterValue mappings out, so editing a Studio Pro call spliced them away (8 mappings → 3).", "file": "sdk/microflows NanoflowParameterValue; mdl/backend/modelsdk microflow_read_actions.go / microflow_write.go (Nanoflows$NanoflowParameterValue), java_write.go codeActionParamTypeToGen (NanoflowType → JavaScriptActions$NanoflowJavaScriptActionParameterType); mdl/executor addCallJavaScriptActionAction, nanoflowParamArgRefusal, describe in cmd_microflows_format_action.go. Tests: *_2450_test.go in executor and modelsdk", "cause": "The JS-action call builder knew only entity-type vs basic parameters, the code-action value model had no nanoflow variant, and describe silently skipped values it could not print. Measuring it found a second gap: create javascript action stored a Nanoflow parameter as String, so no mxcli-authored action could even have one.", "insight": "**A describer that skips an unknown value turns every later edit into data loss.** The splice rebuilds an edited activity from the description, so whatever describe leaves out is deleted on the next change while 'Unchanged' on an untouched re-run hides it. Follow the existing precedent (Java MicroflowParameterValue, #1210/#1282) for name-not-expression and the empty form. Measured on 11.12.6: NanoflowParameterValue written, mx check 0 errors (was CE0117), describe → exec Unchanged, edited call keeps both nanoflow arguments."}
Loading
Loading