fix std control if

[raphael-goetz]

Resolves: #154

[Copilot]

Pull request overview

Fixes an execution bug where std::control::if prematurely terminated flows by emitting a Return signal when the condition was false, and extends the JSON flow test suite to cover if/if_else behavior and expected HTTP response shapes.

Changes:

• Change std::control::if false-branch behavior from Signal::Return(null) to Signal::Success(null) so execution can continue to the next node.
• Fix the test harness so cases that expect a Failure signal can pass when the produced error matches the expected JSON.
• Add new flow-based tests for std::control::if and std::control::if_else, and align several existing flow expectations with current runtime outputs.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
flows/06_if_else_control.json	Adds a flow-based test for std::control::if_else including else-branch behavior and invalid-arg error expectation.
flows/05_if_control.json	Adds a flow-based test for std::control::if to ensure false branch does not terminate execution.
flows/04_example_action.json	Updates expected result to match behavior when remote runtime is not configured.
flows/02_return_flow_input.json	Updates expected HTTP response field name to http_status_code.
flows/01_return_object.json	Updates expected HTTP response field name to http_status_code.
crates/tests/src/main.rs	Fixes test runner logic to treat matching failures as passing cases.
crates/core/src/runtime/functions/control.rs	Fixes std::control::if else-path to emit Success(null) instead of Return(null).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.