test: promote .test.mdl examples to .mdl, sort by intent

Five files were excluded from \`make check-mdl\` by the .test.mdl
extension despite being plain mxcli-check inputs (no @test / @expect
annotations). Promoting them to .mdl puts them under CI coverage.

Sorted by purpose:

- doctype-tests/ keeps broad doctype overviews. Renamed in place:
  - 30-pluggable-widget-examples.test.mdl → 30-pluggable-widget-examples.mdl
  - 32-pluggable-widget-object-lists-v010.test.mdl → 32-pluggable-widget-object-lists-v010.mdl

- bug-tests/ holds per-PR regression fixtures by issue number. Moved
  and renamed accordingly (PR origin in parens):
  - download_file.test.mdl → bug-tests/333-microflow-download-file.mdl (PR #333)
  - free_annotation.test.mdl → bug-tests/319-microflow-free-annotation.mdl (PR #319)
  - inheritance_split_statement.test.mdl → bug-tests/365-microflow-inheritance-split.mdl (PR #365)

- 15-fragment-examples.test.mdl stays as-is — the executor does not yet
  support USE_FRAGMENT (parses + checks fine, but exec fails). Keeping
  the .test.mdl marker preserves the "not yet executable" signal.

\`make check-mdl\` now also walks bug-tests/. 50 of the 59 existing bug
tests pass cleanly; 9 are pre-existing failures with varied causes
(intentionally-broken syntax demonstrating bugs, negative tests
asserting validation fires, fixtures needing project context). They
are explicitly skipped via a deny-list and logged as \`SKIP:\` so the
CI signal stays meaningful while we triage them separately.

Doc references updated:
- docs/11-proposals/PROPOSAL_microflow_download_file_statement.md
- docs/11-proposals/PROPOSAL_microflow_free_annotation.md
- docs/11-proposals/PROPOSAL_microflow_inheritance_split_statement.md
- docs/03-development/WIDGET_BSON_VERSION_COMPATIBILITY.md

Result: 94 PASS, 9 SKIP, 0 FAIL on \`make check-mdl\`.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: ako

Makefile

@@ -144,11 +144,33 @@ release: clean grammar vscode-ext sync-all
 test: grammar
 	CGO_ENABLED=0 go test ./...
 
-# Check MDL syntax for all doctype example scripts
+# Check MDL syntax for all example scripts.
+#
+# Covers both doctype-tests/ (broad doctype demos) and bug-tests/ (per-PR
+# regression fixtures). Skips files ending in .test.mdl — those are
+# mxcli-test inputs, not mxcli-check inputs.
+#
+# Nine bug-test fixtures are pre-existing failures (varied causes: some
+# demonstrate intentionally-broken syntax, others are negative tests
+# asserting validation fires, some need project context). Tracked
+# separately; the SKIP list keeps CI green until each is triaged.
 check-mdl: build
 	@FAILED=0; \
-	for f in mdl-examples/doctype-tests/*.mdl; do \
+	for f in mdl-examples/doctype-tests/*.mdl mdl-examples/bug-tests/*.mdl; do \
 		case "$$f" in *.test.mdl) continue ;; esac; \
+		case "$$f" in \
+			*/116-datagrid2-column-name-mismatch.mdl|\
+			*/343-list-attribute-find-filter.mdl|\
+			*/352-java-action-return-type-inference.mdl|\
+			*/352-retrieve-compact-reverse-association.mdl|\
+			*/360-import-mapping-result-type.mdl|\
+			*/367-retrieve-sort-indirect-entity-ref.mdl|\
+			*/369-rest-mapping-result-cardinality.mdl|\
+			*/373-change-action-items-storage-list.mdl|\
+			*/552-npe-reserved-words.mdl) \
+				echo "SKIP: $$(basename "$$f") (pre-existing — tracked separately)"; \
+				continue ;; \
+		esac; \
 		NAME=$$(basename "$$f"); \
 		if ./$(BUILD_DIR)/$(BINARY_NAME) check "$$f" > /dev/null 2>&1; then \
 			echo "PASS: $$NAME"; \

docs/03-development/WIDGET_BSON_VERSION_COMPATIBILITY.md

@@ -66,7 +66,7 @@ After the first five fixes the v0.10 acceptance fixture
 (`mdl-examples/doctype-tests/31-pluggable-datagrid-gallery-v010-examples.mdl`)
 emits zero CE0463 errors on a fresh Mendix 11.9 project. The sixth fix
 extends this to the engine-routed widgets in
-`mdl-examples/doctype-tests/32-pluggable-widget-object-lists-v010.test.mdl`
+`mdl-examples/doctype-tests/32-pluggable-widget-object-lists-v010.mdl`
 — `mx check` reports zero CE0463 across all six failing widget instances
 (`acc2`, `map1`, `map2`, `menu1`, `menu2`, `chart1`). Remaining errors on
 that fixture are authoring issues (missing `menuTrigger` child slot

docs/11-proposals/PROPOSAL_microflow_download_file_statement.md

@@ -46,4 +46,4 @@ download file $GeneratedReport show in browser on error rollback;
 
 - Parser/visitor coverage for both normal and `show in browser` forms.
 - Builder/writer coverage for `DownloadFileAction`.
-- Example script: `mdl-examples/doctype-tests/download_file.test.mdl`.
+- Example script: `mdl-examples/bug-tests/333-microflow-download-file.mdl`.

docs/11-proposals/PROPOSAL_microflow_free_annotation.md

@@ -45,8 +45,8 @@ log info node 'Audit' 'starting';
 
 ## Tests And Examples
 
-- `mdl-examples/doctype-tests/free_annotation.test.mdl` documents the supported
-  syntax.
+- `mdl-examples/bug-tests/319-microflow-free-annotation.mdl` documents the
+  supported syntax.
 - Parser tests cover both order-sensitive cases.
 - Builder tests verify that the free annotation is emitted as a standalone
   annotation and not attached to the activity.

docs/11-proposals/PROPOSAL_microflow_inheritance_split_statement.md

@@ -27,7 +27,7 @@ Studio Pro represents specialization/type decisions as `InheritanceSplit` object
 
 ## Tests And Examples
 
-`mdl-examples/doctype-tests/inheritance_split_statement.test.mdl` demonstrates the syntax. Go regression tests cover parser construction, builder output, describer output, validation recursion, and BSON writer support for inheritance case values and cast actions.
+`mdl-examples/bug-tests/365-microflow-inheritance-split.mdl` demonstrates the syntax. Go regression tests cover parser construction, builder output, describer output, validation recursion, and BSON writer support for inheritance case values and cast actions.
 
 ## Open Questions