fix: positional step params no longer carry the label prefix into XML

[fuzzzerd]

Summary

FmScript.SynthesizeHrParams blindly converted every entry in the caller's param map into "{Key}: {Value}" regardless of whether the underlying step param had a display label. Steps whose params are positional (no HrLabel in their metadata) received the dict key as a literal prefix into XML.

Concrete impact for MCP / external callers using update_script_steps with structured params:

Step	Param	Before	After
Set Variable	Name	<Name>Name: $i</Name>	<Name>$i</Name>
If / Else If / Exit Loop If	condition	<Calculation>condition: $i &gt; $limit</Calculation>	<Calculation>$i &gt; $limit</Calculation>

The bad XML imports into FileMaker successfully (it's structurally valid) but produces silent runtime errors because the variable name / calculation now contains an extraneous "label: " prefix.

Fix

SynthesizeHrParams now consults StepMetadata.Params to drive output:

• Iterates metadata in declared order (positional correctness)
• Formats with HrLabel when defined; raw when not
• Case-insensitive key matching
• Forward-compat: unknown keys fall through with the previous labeled formatting so newly-introduced params keep working until their metadata catches up

Test plan

• Six new regression tests under tests/SharpFM.Tests/Scripting/FmScriptApplyTests.cs cover Set Variable, If, Exit Loop If, out-of-order params, case-insensitive keys, and the update path
• Full test suite green (1174 SharpFM.Tests + 92 SharpFM.Plugin.Tests)
• Manually verify a generated FizzBuzz script imports and runs in FileMaker

[github-actions]

Test Results

✔️ Tests 1260 / 1260 - passed in 13.5s
✔️ Coverage 78.38% - passed with 70% threshold
📏 14433 / 16876 lines covered 🌿 4913 / 7806 branches covered
🔍 click here for more details

✏️ updated for commit e5009d4