docs: clarify ParameterMappings storage-list marker comment

The legacy SOAP writer had a misleading comment claiming the leading
`int32(2)` of an empty ParameterMappings array was a "declared count".
It is actually the Mendix storage-list-type marker — the same
constant used by every other empty list writer in this file (see
PR #338 for showpage and PR #374 for change-action items).

Addresses ako's review on PR #334.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Author: hjothamendix

mdl/executor/cmd_microflows_builder.go

@@ -53,7 +53,7 @@ type flowBuilder struct {
 	microflowsCacheLoaded bool
 	nanoflowsCache        []*microflows.Nanoflow
 	nanoflowsCacheLoaded  bool
-	manualLoopBackTarget model.ID
+	manualLoopBackTarget  model.ID
 }
 
 // addError records a validation error during flow building.

sdk/mpr/writer_microflow_actions.go

@@ -702,10 +702,12 @@ func serializeWebServiceCallAction(a *microflows.WebServiceCallAction) bson.D {
 				{Key: "$ID", Value: idToBsonBinary(GenerateID())},
 				{Key: "$Type", Value: "Microflows$ExportMappingCall"},
 				{Key: "Mapping", Value: string(a.SendMappingID)},
-				// Studio Pro uses an array whose first element is the declared
-				// count. The legacy SOAP fixture has no parameter mappings, so
-				// this marker matches the empty ExportMappingCall shape used by
-				// existing microflow/rule-call writers.
+				// Mendix storage lists encode their first element as a
+				// constant storage-list-type marker (`2` for object lists),
+				// NOT the element count. The empty ExportMappingCall shape
+				// used by other writers in this file follows the same
+				// convention; see #338 / #374 for prior fixes that aligned
+				// other writers on this marker.
 				{Key: "ParameterMappings", Value: bson.A{int32(2)}},
 			}},
 		}})