`check --references` passes a `CHANGE $Obj ("Attr" = …)` whose attribute does NOT exist on the entity; `exec` writes it; `mx check` → CE1613

[marclehane-creator]

Found by accident while testing the guard on a FRESH copy (17:48Z): the script contained only the
microflow, not the ALTER ENTITY … ADD ATTRIBUTE that should have preceded it.

CREATE OR MODIFY MICROFLOW AgencyAndProgram.ACT_Program_Archive ($Program: AgencyAndProgram.Program) RETURNS void BEGIN
  CHANGE $Program ("IsArchived" = true);   -- IsArchived does not exist on Program in this copy
  COMMIT $Program;
END;

rung	result
check script.mdl -p App.mpr --references	exit 0 (references "valid")
exec	Created microflow (exit 0)
mx check	[error] [CE1613] "The selected attribute 'AgencyAndProgram.Program.IsArchived' no longer exists." at Change object activity 'Change 'Program' (IsArchived)'

--references resolves the entity AgencyAndProgram.Program (it exists) but not the attribute named
inside the CHANGE's member list, although the catalog it builds lists every attribute (✓ Attributes: 232 in the fixture). Same family as 0.19.0 §3.1 and Issue 79; for a generate→verify loop it means a
mistyped attribute name is only caught by the compiler. Ask: validate CHANGE / CREATE member names
against the entity in --references mode.

---

mxcli 0.20.0, Mendix 11.12.x, Windows 11. Found while evaluating a self-hosted agent loop that drives check → check --references → exec → mx check; each item above was reproduced on a fresh copy of the fixture or app named.