Fix incorrect Direction for max parameter in InRangeCall/OutRangeCall

[Copilot]

Both InRangeCall and OutRangeCall incorrectly assigned Direction.Output to the max parameter — it's an input bound, not an output.

Changes

• InRangeCall.cs / OutRangeCall.cs: Changed max parameter direction from Direction.Output → Direction.Input, consistent with min and in

// Before (wrong)
Interface["max"] = new IOperationOrSignalDirectionWrapper(max, Direction.Output);

// After (correct)
Interface["max"] = new IOperationOrSignalDirectionWrapper(max, Direction.Input);

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Fix issues in InRangeCall/OutRangeCall copilot found in #21</issue_title>
<issue_description></issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Fix issues in InRangeCall/OutRangeCall copilot found in #21 #22

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.