Please address the comments from this code review:

## Overall Comments
- The new `jump_back` field on `NodeDetail` is not included in the `MEO_TOJSON` macro call, so its value will not be serialized; consider adding it there (and to any corresponding deserialization, if applicable) to keep the result schema consistent.
- The logic to resolve `jump_back` based on `next` and `get_pipeline_data` now lives in `run_next` while `run` only consumes the propagated flag; if this resolution is needed elsewhere, consider extracting it into a small helper to avoid future drift in behavior.

## Individual Comments

### Comment 1
<location path="source/include/Common/TaskResultTypes.h" line_range="47-49" />
<code_context>
     MaaRecoId reco_id = MaaInvalidId;
     MaaActId action_id = MaaInvalidId;
     bool completed = false;
+    bool jump_back = false;

     MEO_TOJSON(node_id, name, reco_id, action_id, completed);
 };
</code_context>
<issue_to_address>
**issue (bug_risk):** Include `jump_back` in the serialization macro to keep JSON in sync with the struct

`jump_back` was added to `NodeDetail` but not to `MEO_TOJSON(...)`, so it won’t be included in JSON and the wire format will diverge from the struct. Please add `jump_back` to the macro arguments so JSON-based consumers stay consistent with the in-memory representation.
</issue_to_address>