fix: address SOAP statement review feedback

Symptom: the call web service doctype example used a skipped .test.mdl suffix, and the grammar/docs did not explain why structured SOAP references are quoted strings.

Root cause: legacy SOAP support intentionally accepts both Module.Document text and raw dangling IDs, but that design choice was only implicit in examples.

Fix: rename the doctype example to a checked .mdl fixture and document the STRING_LITERAL reference choice in the grammar, skill, proposal, and quick reference.

Tests: ran make build, mxcli check on the doctype fixture, and make test.

Author: hjothamendix

.claude/skills/mendix/write-microflows.md

@@ -736,7 +736,9 @@ for new integrations; this syntax exists mainly so existing projects can
 round-trip without dropping SOAP actions.
 
 ```mdl
--- Structured form. DESCRIBE prefers Module.Document names when references are resolvable.
+-- Structured form. SOAP references are quoted strings by design: DESCRIBE
+-- prefers Module.Document names when references are resolvable, but raw IDs
+-- and legacy document names must also round-trip.
 $Root = call web service 'SampleSOAP.OrderService'
 operation 'FetchSampleItems'
 send mapping 'SampleSOAP.OrderRequest'

docs/01-project/MDL_QUICK_REFERENCE.md

@@ -228,7 +228,7 @@ authentication basic, session
 | Call nanoflow | `$Result = call nanoflow Module.Name (Param = $value);` | |
 | Call JS action | `$Result = call javascript action Module.Name (Param = $value);` | JavaScript action (nanoflow/microflow) |
 | Call Java action | `$Result = call java action Module.Name (Param = $value);` | Java action (microflow only) |
-| Call web service | `$Result = call web service 'Module.Service' operation 'OperationName';` | Legacy SOAP; unresolved dangling refs fall back to raw IDs |
+| Call web service | `$Result = call web service 'Module.Service' operation 'OperationName';` | Legacy SOAP; quoted refs preserve raw IDs and legacy names |
 | Call web service raw | `$Result = call web service raw 'base64-bson';` | Escape hatch for byte-for-byte legacy SOAP round-trip |
 | Show page | `show page Module.PageName ($Param = $value);` | Also accepts `(Param: $value)` |
 | Close page | `close page;` | |

docs/11-proposals/PROPOSAL_microflow_call_web_service_statement.md

@@ -75,13 +75,18 @@ syntax covers them.
 - Builder/writer coverage for real `WebServiceCallAction` construction and raw
   BSON preservation.
 - Formatter coverage for qualified-name resolution and raw-ID fallback.
-- Example script: `mdl-examples/doctype-tests/call_web_service.test.mdl`.
+- Example script: `mdl-examples/doctype-tests/call_web_service.mdl`.
 
 ## Resolved Questions
 
 - Service and mapping references are emitted as `Module.Document` names when
   the backend can resolve them. Raw IDs remain the fallback for dangling
   references and incomplete project metadata.
+- The structured syntax uses quoted strings for service and mapping references
+  instead of `qualifiedName` tokens because legacy SOAP projects can contain
+  raw IDs or document names that are not valid MDL identifiers. Resolved
+  references should still be written as `Module.Document` text inside the
+  string literal.
 
 ## Open Questions
 

…/doctype-tests/call_web_service.test.mdl …mples/doctype-tests/call_web_service.mdlmdl-examples/doctype-tests/call_web_service.test.mdl renamed to mdl-examples/doctype-tests/call_web_service.mdl mdl-examples/doctype-tests/call_web_service.test.mdl renamed to mdl-examples/doctype-tests/call_web_service.mdl

@@ -1490,8 +1490,12 @@ callJavaScriptActionStatement
     : (VARIABLE EQUALS)? CALL JAVASCRIPT ACTION qualifiedName LPAREN callArgumentList? RPAREN onErrorClause?
     ;
 
-// Legacy SOAP call. The preferred structured form uses Module.Document names;
-// raw IDs remain accepted for dangling references and old round-trip output.
+// Legacy SOAP call. The preferred structured form stores service and mapping
+// references in STRING_LITERAL tokens rather than qualifiedName tokens because
+// old projects can contain raw IDs or SOAP document names that are not valid
+// MDL identifiers. DESCRIBE still prefers Module.Document text when references
+// resolve; unresolved values pass through as strings. Raw BSON remains the
+// escape hatch for unsupported SOAP payload details.
 callWebServiceStatement
     : (VARIABLE EQUALS)? CALL WEB SERVICE
       (RAW STRING_LITERAL