DESCRIBE does not print conditional visibility on layout-grid rows and columns, so restating a page makes every row always visible #1461

Summary

A layout-grid row (and column) can carry its own conditional visibility in Studio Pro. DESCRIBE does not print it. A page rebuilt from DESCRIBE output would lose every such rule without a warning, and the build would stay clean.

In one app, two edit pages show nine detail sections by type through row visibility, and one snippet has 56 row-level "show only when it has a value" rules. None of them appear in DESCRIBE.

Environment

• mxcli v0.25.0 (2026-10-05), macOS arm64
• Mendix 11.14.0 Beta project (existing app, upgraded), MPR v2, Classic (Dojo) web client, security level Production
• Re-read on main (2026-10-13): rawWidgetRow and rawWidgetColumn in mdl/executor/cmd_pages_describe.go have no visibility field, and parseLayoutGridRows (cmd_pages_describe_parse.go) does not read ConditionalVisibilitySettings. v0.26.0's release notes say rows and columns now keep design properties, classes, styles and alignment; visibility is not listed.
• mxcli diag --bundle is not attached because the project is a customer app.

Steps to reproduce

1. In Studio Pro, on a page MyModule.Account_Edit with a data view over MyModule.Account, put a layout grid inside the data view. Give its second row a visibility condition, for example based on MyModule.Account.Type = Business. Save.
2. mxcli -p App.mpr -c "describe page MyModule.Account_Edit".

Expected

The row is printed with its condition, for example row (Visible: $currentObject/Type = MyModule.AccountType.Business) { … } (or the attribute form Visible: Type in (Business)), and create / alter write it back. If that is not supported yet, a comment says the row's visibility was left out.

Actual

The row is printed as row { … } with no condition and no comment. We confirmed the conditions in the stored BSON. We did not test whether Visible: on a row is accepted on write.

Workaround used

Our drafters read each row rule from the BSON and rewrote it as a container with Visible: inside the column. DESCRIBE prints container visibility, so the rebuilt pages round-trip. An audit confirmed every rule was carried over.

Suggested fix

1. Read ConditionalVisibilitySettings on layout-grid rows and columns in DESCRIBE, in both forms (expression and attribute-based), and print them with the same Visible: syntax used on widgets.
2. Accept Visible: on row and column in create, replace and alter.
3. Until then, print an "omitted" comment on the affected row.

Related: the role-based visibility issue filed alongside this one (same silent-loss pattern, different setting).