Classify widget BSON drift after .mpk upgrade

[ako]

Parent: #540 (v0.11.0 workflow integration)

Goal

When a project's `.mpk` widget package is upgraded, classify the BSON-level impact of the schema change so authors know whether they need to open Studio Pro to repair widgets or whether mxcli can patch them automatically.

Background

#540 listed this as work:

Classify widget BSON drift after a `.mpk` upgrade (additive-safe vs needs Studio Pro intervention)

It wasn't delivered with #540's diagnostics/completion work — this is closer to a migration command than to an authoring-time validator, and probably overlaps with the planned `mxcli widget upgrade` work (out of scope for v0.11 per the issue body).

Work

• Build a diff between the previously-cached `.def.json` and the freshly-extracted one
• Classify each property change:
  • Additive-safe: new property with a default → no project changes needed
  • Default changed: existing widgets keep their old value, new widgets get new default → informational
  • Type changed: existing widgets may have BSON inconsistent with new schema → needs Studio Pro intervention
  • Property removed: existing widget BSON has orphan keys → needs Studio Pro intervention
• Surface a summary in `mxcli refresh catalog` output (next to the current `✓ datagrid: v2.22.0 → v2.30.1 (4 new properties, 1 default changed)` line, which is currently mocked rather than computed)
• Optional: `mxcli widget upgrade --dry-run` command listing affected pages/snippets

Acceptance criteria

• `mxcli refresh catalog` accurately reports additive vs breaking schema changes
• Breaking changes name the affected pages/snippets in the project so the author can locate them in Studio Pro

Out of scope

• Auto-patching widget BSON in MPR files (likely never — Studio Pro should own that)
• Per-property semver tracking — comparison is between local cache and current `.mpk`, not against a remote catalog

[github-actions]

Issue Triage

Summary
The issue requests a feature that classifies widget BSON schema changes after an .mpk upgrade so users can tell whether mxcli can handle the change automatically or if Studio Pro intervention is required.

Checklist for feature request

Required info	Present?	Details
Use case – why the feature is needed / problem it solves	✅	Described in “Goal” and “Background”: need to know if widget BSON drift is additive‑safe or requires Studio Pro repair.
Proposed syntax or behavior (if applicable)	✅	Described in “Work”: diff cached .def.json vs extracted one, classify property changes, surface summary in mxcli refresh catalog, optional mxcli widget upgrade --dry-run.
Mendix version relevance (if version‑specific)	❌	No explicit mention of which Mendix versions the feature targets or any version‑specific constraints.

Polite request for missing information
Could you let us know which Mendix version(s) this feature should target (e.g., MX 9, MX 10, or all versions)? If it’s version‑agnostic, a brief note confirming that would be helpful. Thank you!

---

Automated triage via OpenRouter — workflow source