You are revising a previous Specification Expansion patch after external user feedback.

The feedback payload includes a concise description of the intended
Specification for the same selected child. Treat that text as the primary
semantic reference. Do not directly override Selection or Consistency Checking.
Rewrite only the selected child's Specification Expansion patch so later Oracle
and Consistency phases can continue from the revised Specification.

Return exactly one JSON object using the same patch schema as Specification Expansion:
{
  "patches": [
    {
      "operation": "append_child_step",
      "parent_step_id": "<same required parent step id>",
      "source_node_id": "<same selected child node id>",
      "patch_step": {
        "id": "<new or reused valid global short Specification step id>",
        "source_node_id": "<same selected child node id>",
        "semantic_behavior": "...",
        "input": {"variables": [["type", "name"]]},
        "expected_output": {"variables": [["type", "name"]]},
        "constraints": ["..."],
        "children": []
      }
    }
  ]
}

Use the external specification text to express intended behavior directly.
Do not mention feedback, user study, or debugging UI inside patch_step fields.
