Two lint rules a real project asked for, and a describe → check round trip that was failing on 6 of 14 workflows

[ako]

Four commits: two new lint rules, one round-trip fix, one proposal.

describe workflow emitted MDL that mxcli check refused

6 of the 14 workflows across the 9 demo apps in mx-test-projects/ failed describe → check. Two independent defects behind one symptom.

MDL-WF03 refused the enumeration value Studio Pro actually stores. The rule required a bare identifier, but every Workflows$EnumerationValueConditionOutcome in the corpus holds the qualified Module.Enum.Value form — 7 of 7 non-empty — so the describer emitted what was stored and the checker rejected mxcli's own output. The rule exists to catch free text like 'Confirmed closed'; rejecting the dot was collateral, and spaces are still refused. The stored document is what settled which side to change: emitting the last segment instead would have quieted check and written a document unlike every real one.

MDL could not name the activities a jump to targets. Mendix stores JumpToActivity.TargetActivity as an activity name string, not a pointer, and Studio Pro names activities by type and ordinal (decision1, split1, callMicroflow1) with no relation to the caption. MDL had a name slot only on user task; every other builder did act.Name = act.Caption, so the stored name had nowhere to be emitted to, two decisions sharing a caption collided on one name, and jump to decision1 resolved to nothing. Reaching MxBuild it became a jump to itself and surfaced as CE6681 — "not possible to jump to end activities or jump-to activities" — an error naming a different fault.

That was not a describer bug, so the fix runs the full width: grammar → AST → visitor → builder → describer. decision, parallel split, wait for timer and wait for notification now take an optional name; call microflow / call workflow take AS <name>. Without one the caption-derived name is unchanged, so existing scripts are unaffected.

Two lint rules, both narrowed by measurement

CONV018 — a module never organised into folders. A project with 200 documents loose in one flat module scored clean across all three rule sets. The rule fires only when both halves hold: more than max_root_documents (default 20) sit directly in the module root, and not one document in the module is in a folder.

The second half is what stops it nagging. A module that has started to organise itself — even one folder — is never reported however much remains at its root: the team has evidently made a choice, and a linter guessing at the rest is noise.

Only kinds Studio Pro actually lets you file in a folder are counted, as an allow-list rather than a deny-list. An association belongs to the domain model and an external entity to a consumed service, so counting them would report a module as unorganised on the strength of elements nobody can move. The polarity is deliberate: a document type missing from the list is undercounted, so the rule stays quiet rather than inventing a violation.

CONV019 — a navigation screen that cannot be linked to. A Mendix page is reachable at /p/<url> only if it has been given a URL. Without one it exists solely at the end of a click path: no bookmark, no link from an email, no reopen after refresh, and no mxcli run --local --screenshot-url — so verifying one screen means driving a browser through login and the menu.

The rule reports only the pages a navigation profile routes to — profile home, role homes, menu targets. That narrowing is the whole design, and it is measured rather than assumed: on a blank Mendix 11.12.1 app, 0 of 16 pages carry a URL, Mendix's own Home page included. Reporting every page without one would warn about every page of every project from the day it is created.

Never reported, each for its own reason: login and not-found pages (the platform routes to those itself), microflow-valued menu items and home pages (the microflow decides what opens, so there is no page to be addressable), and System or Marketplace targets. A page routed to several ways is one finding naming every route.

Both rules needed new Starlark builtins, and those are the reusable part: documents() exposes every element of the App Explorer tree as (kind, name, qualified_name, module_name, folder) read from the catalog's objects view — so a new document type is covered for free — and navigation_targets() gives (profile, kind, role, caption, page) for every routed-to page. Navigation was previously reachable only from the Go rules, so no Starlark rule could ask which pages a user can actually reach.

Proposal

Offline synchronization configuration. mxcli can create an offline navigation profile and read every row of its sync config, but cannot write one — so the profile builds, routes, installs as a PWA and shows an empty app. Two hazards documented before any code: the read is already lossy (gen declares six properties on the config element, the semantic model keeps three), and the sync mode is an enum whose Studio Pro captions are not its keys — the same shape as the CE0463 gallery defect. Draft; no code