Upload current ExeWorldBench dataset (part 3)

t2/task/05_01/05_01.txt

@@ -0,0 +1,75 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+05_01
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/05_01/test_05_01.png
+
+Use only the reference image explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task/05_01
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/05_01. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given a visual reference of a multi-stage mechanical chain.
+
+The visual reference mainly specifies the mechanical components involved and their approximate spatial arrangement, but the exact positions, distances, orientations, and geometric relationships may not directly form an executable mechanical system.
+
+Your task is to reason about how the components should mechanically interact, adjust their spatial configuration when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the static appearance of the reference, but to construct a physically executable mechanical system in which the initial action propagates through all stages and completes the intended chain reaction.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure shown in the reference.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, or other geometric relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- Do not directly prescribe the per-frame position or rotation of components to reproduce the expected animation.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The animation must be long enough to show the complete mechanical chain.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual reference as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task/05_01/05_01.py
+* /xxx/ExeWorldBench/t2/task/05_01/05_01.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t2/task/05_02/05_02.txt

@@ -0,0 +1,75 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+05_02
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/05_02/test_05_02.png
+
+Use only the reference image explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task/05_02
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/05_02. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given a visual reference of a multi-stage mechanical chain.
+
+The visual reference mainly specifies the mechanical components involved and their approximate spatial arrangement, but the exact positions, distances, orientations, and geometric relationships may not directly form an executable mechanical system.
+
+Your task is to reason about how the components should mechanically interact, adjust their spatial configuration when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the static appearance of the reference, but to construct a physically executable mechanical system in which the initial action propagates through all stages and completes the intended chain reaction.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure shown in the reference.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, or other geometric relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- Do not directly prescribe the per-frame position or rotation of components to reproduce the expected animation.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The animation must be long enough to show the complete mechanical chain.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual reference as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task/05_02/05_02.py
+* /xxx/ExeWorldBench/t2/task/05_02/05_02.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t2/task/05_03/05_03.txt

@@ -0,0 +1,75 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+05_03
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/05_03/test_05_03.png
+
+Use only the reference image explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task/05_03
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/05_03. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given a visual reference of a multi-stage mechanical chain.
+
+The visual reference mainly specifies the mechanical components involved and their approximate spatial arrangement, but the exact positions, distances, orientations, and geometric relationships may not directly form an executable mechanical system.
+
+Your task is to reason about how the components should mechanically interact, adjust their spatial configuration when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the static appearance of the reference, but to construct a physically executable mechanical system in which the initial action propagates through all stages and completes the intended chain reaction.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure shown in the reference.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, or other geometric relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- Do not directly prescribe the per-frame position or rotation of components to reproduce the expected animation.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The animation must be long enough to show the complete mechanical chain.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual reference as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task/05_03/05_03.py
+* /xxx/ExeWorldBench/t2/task/05_03/05_03.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t2/task/05_04/05_04.txt

@@ -0,0 +1,75 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+05_04
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/05_04/test_05_04.png
+
+Use only the reference image explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task/05_04
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/05_04. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given a visual reference of a multi-stage mechanical chain.
+
+The visual reference mainly specifies the mechanical components involved and their approximate spatial arrangement, but the exact positions, distances, orientations, and geometric relationships may not directly form an executable mechanical system.
+
+Your task is to reason about how the components should mechanically interact, adjust their spatial configuration when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the static appearance of the reference, but to construct a physically executable mechanical system in which the initial action propagates through all stages and completes the intended chain reaction.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure shown in the reference.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, or other geometric relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- Do not directly prescribe the per-frame position or rotation of components to reproduce the expected animation.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The animation must be long enough to show the complete mechanical chain.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual reference as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task/05_04/05_04.py
+* /xxx/ExeWorldBench/t2/task/05_04/05_04.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t2/task/05_05/05_05.txt

@@ -0,0 +1,75 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+05_05
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/05_05/test_05_05.png
+
+Use only the reference image explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task/05_05
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/05_05. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given a visual reference of a multi-stage mechanical chain.
+
+The visual reference mainly specifies the mechanical components involved and their approximate spatial arrangement, but the exact positions, distances, orientations, and geometric relationships may not directly form an executable mechanical system.
+
+Your task is to reason about how the components should mechanically interact, adjust their spatial configuration when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the static appearance of the reference, but to construct a physically executable mechanical system in which the initial action propagates through all stages and completes the intended chain reaction.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure shown in the reference.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, or other geometric relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- Do not directly prescribe the per-frame position or rotation of components to reproduce the expected animation.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The animation must be long enough to show the complete mechanical chain.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual reference as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task/05_05/05_05.py
+* /xxx/ExeWorldBench/t2/task/05_05/05_05.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t2/task/05_06/05_06.txt

@@ -0,0 +1,75 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+05_06
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/05_06/test_05_06.png
+
+Use only the reference image explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task/05_06
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/05_06. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given a visual reference of a multi-stage mechanical chain.
+
+The visual reference mainly specifies the mechanical components involved and their approximate spatial arrangement, but the exact positions, distances, orientations, and geometric relationships may not directly form an executable mechanical system.
+
+Your task is to reason about how the components should mechanically interact, adjust their spatial configuration when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the static appearance of the reference, but to construct a physically executable mechanical system in which the initial action propagates through all stages and completes the intended chain reaction.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure shown in the reference.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, or other geometric relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- Do not directly prescribe the per-frame position or rotation of components to reproduce the expected animation.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The animation must be long enough to show the complete mechanical chain.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual reference as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task/05_06/05_06.py
+* /xxx/ExeWorldBench/t2/task/05_06/05_06.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t2/task/05_07/05_07.txt

@@ -0,0 +1,75 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+05_07
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/05_07/test_05_07.png
+
+Use only the reference image explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task/05_07
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/05_07. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given a visual reference of a multi-stage mechanical chain.
+
+The visual reference mainly specifies the mechanical components involved and their approximate spatial arrangement, but the exact positions, distances, orientations, and geometric relationships may not directly form an executable mechanical system.
+
+Your task is to reason about how the components should mechanically interact, adjust their spatial configuration when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the static appearance of the reference, but to construct a physically executable mechanical system in which the initial action propagates through all stages and completes the intended chain reaction.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure shown in the reference.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, or other geometric relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- Do not directly prescribe the per-frame position or rotation of components to reproduce the expected animation.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The animation must be long enough to show the complete mechanical chain.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual reference as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task/05_07/05_07.py
+* /xxx/ExeWorldBench/t2/task/05_07/05_07.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t2/task/05_08/05_08.txt

@@ -0,0 +1,75 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+05_08
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/05_08/test_05_08.png
+
+Use only the reference image explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task/05_08
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/05_08. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given a visual reference of a multi-stage mechanical chain.
+
+The visual reference mainly specifies the mechanical components involved and their approximate spatial arrangement, but the exact positions, distances, orientations, and geometric relationships may not directly form an executable mechanical system.
+
+Your task is to reason about how the components should mechanically interact, adjust their spatial configuration when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the static appearance of the reference, but to construct a physically executable mechanical system in which the initial action propagates through all stages and completes the intended chain reaction.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure shown in the reference.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, or other geometric relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- Do not directly prescribe the per-frame position or rotation of components to reproduce the expected animation.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The animation must be long enough to show the complete mechanical chain.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual reference as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task/05_08/05_08.py
+* /xxx/ExeWorldBench/t2/task/05_08/05_08.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t2/task/05_09/05_09.txt

@@ -0,0 +1,75 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+05_09
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/05_09/test_05_09.png
+
+Use only the reference image explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task/05_09
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/05_09. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given a visual reference of a multi-stage mechanical chain.
+
+The visual reference mainly specifies the mechanical components involved and their approximate spatial arrangement, but the exact positions, distances, orientations, and geometric relationships may not directly form an executable mechanical system.
+
+Your task is to reason about how the components should mechanically interact, adjust their spatial configuration when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the static appearance of the reference, but to construct a physically executable mechanical system in which the initial action propagates through all stages and completes the intended chain reaction.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure shown in the reference.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, or other geometric relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- Do not directly prescribe the per-frame position or rotation of components to reproduce the expected animation.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The animation must be long enough to show the complete mechanical chain.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual reference as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task/05_09/05_09.py
+* /xxx/ExeWorldBench/t2/task/05_09/05_09.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t2/task/05_10/05_10.txt

@@ -0,0 +1,75 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+05_10
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/05_10/test_05_10.png
+
+Use only the reference image explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task/05_10
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/05_10. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given a visual reference of a multi-stage mechanical chain.
+
+The visual reference mainly specifies the mechanical components involved and their approximate spatial arrangement, but the exact positions, distances, orientations, and geometric relationships may not directly form an executable mechanical system.
+
+Your task is to reason about how the components should mechanically interact, adjust their spatial configuration when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the static appearance of the reference, but to construct a physically executable mechanical system in which the initial action propagates through all stages and completes the intended chain reaction.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure shown in the reference.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, or other geometric relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- Do not directly prescribe the per-frame position or rotation of components to reproduce the expected animation.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The animation must be long enough to show the complete mechanical chain.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual reference as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task/05_10/05_10.py
+* /xxx/ExeWorldBench/t2/task/05_10/05_10.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t2/task/06_01/06_01.txt

@@ -0,0 +1,75 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+06_01
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/06_01/test_06_01.png
+
+Use only the reference image explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task/06_01
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/06_01. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given a visual reference of a multi-stage mechanical chain.
+
+The visual reference mainly specifies the mechanical components involved and their approximate spatial arrangement, but the exact positions, distances, orientations, and geometric relationships may not directly form an executable mechanical system.
+
+Your task is to reason about how the components should mechanically interact, adjust their spatial configuration when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the static appearance of the reference, but to construct a physically executable mechanical system in which the initial action propagates through all stages and completes the intended chain reaction.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure shown in the reference.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, or other geometric relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- Do not directly prescribe the per-frame position or rotation of components to reproduce the expected animation.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The animation must be long enough to show the complete mechanical chain.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual reference as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task/06_01/06_01.py
+* /xxx/ExeWorldBench/t2/task/06_01/06_01.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t2/task/06_02/06_02.txt

@@ -0,0 +1,75 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+06_02
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/06_02/test_06_02.png
+
+Use only the reference image explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task/06_02
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/06_02. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given a visual reference of a multi-stage mechanical chain.
+
+The visual reference mainly specifies the mechanical components involved and their approximate spatial arrangement, but the exact positions, distances, orientations, and geometric relationships may not directly form an executable mechanical system.
+
+Your task is to reason about how the components should mechanically interact, adjust their spatial configuration when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the static appearance of the reference, but to construct a physically executable mechanical system in which the initial action propagates through all stages and completes the intended chain reaction.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure shown in the reference.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, or other geometric relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- Do not directly prescribe the per-frame position or rotation of components to reproduce the expected animation.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The animation must be long enough to show the complete mechanical chain.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual reference as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task/06_02/06_02.py
+* /xxx/ExeWorldBench/t2/task/06_02/06_02.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t2/task/06_03/06_03.txt

@@ -0,0 +1,75 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+06_03
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/06_03/test_06_03.png
+
+Use only the reference image explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task/06_03
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/06_03. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given a visual reference of a multi-stage mechanical chain.
+
+The visual reference mainly specifies the mechanical components involved and their approximate spatial arrangement, but the exact positions, distances, orientations, and geometric relationships may not directly form an executable mechanical system.
+
+Your task is to reason about how the components should mechanically interact, adjust their spatial configuration when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the static appearance of the reference, but to construct a physically executable mechanical system in which the initial action propagates through all stages and completes the intended chain reaction.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure shown in the reference.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, or other geometric relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- Do not directly prescribe the per-frame position or rotation of components to reproduce the expected animation.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The animation must be long enough to show the complete mechanical chain.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual reference as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task/06_03/06_03.py
+* /xxx/ExeWorldBench/t2/task/06_03/06_03.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t2/task/06_04/06_04.txt

@@ -0,0 +1,75 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+06_04
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/06_04/test_06_04.png
+
+Use only the reference image explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task/06_04
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/06_04. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given a visual reference of a multi-stage mechanical chain.
+
+The visual reference mainly specifies the mechanical components involved and their approximate spatial arrangement, but the exact positions, distances, orientations, and geometric relationships may not directly form an executable mechanical system.
+
+Your task is to reason about how the components should mechanically interact, adjust their spatial configuration when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the static appearance of the reference, but to construct a physically executable mechanical system in which the initial action propagates through all stages and completes the intended chain reaction.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure shown in the reference.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, or other geometric relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- Do not directly prescribe the per-frame position or rotation of components to reproduce the expected animation.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The animation must be long enough to show the complete mechanical chain.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual reference as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task/06_04/06_04.py
+* /xxx/ExeWorldBench/t2/task/06_04/06_04.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t2/task/06_05/06_05.txt

@@ -0,0 +1,75 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+06_05
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/06_05/test_06_05.png
+
+Use only the reference image explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task/06_05
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/06_05. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given a visual reference of a multi-stage mechanical chain.
+
+The visual reference mainly specifies the mechanical components involved and their approximate spatial arrangement, but the exact positions, distances, orientations, and geometric relationships may not directly form an executable mechanical system.
+
+Your task is to reason about how the components should mechanically interact, adjust their spatial configuration when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the static appearance of the reference, but to construct a physically executable mechanical system in which the initial action propagates through all stages and completes the intended chain reaction.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure shown in the reference.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, or other geometric relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- Do not directly prescribe the per-frame position or rotation of components to reproduce the expected animation.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The animation must be long enough to show the complete mechanical chain.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual reference as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task/06_05/06_05.py
+* /xxx/ExeWorldBench/t2/task/06_05/06_05.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t2/task/06_06/06_06.txt

@@ -0,0 +1,75 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+06_06
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/06_06/test_06_06.png
+
+Use only the reference image explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task/06_06
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/06_06. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given a visual reference of a multi-stage mechanical chain.
+
+The visual reference mainly specifies the mechanical components involved and their approximate spatial arrangement, but the exact positions, distances, orientations, and geometric relationships may not directly form an executable mechanical system.
+
+Your task is to reason about how the components should mechanically interact, adjust their spatial configuration when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the static appearance of the reference, but to construct a physically executable mechanical system in which the initial action propagates through all stages and completes the intended chain reaction.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure shown in the reference.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, or other geometric relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- Do not directly prescribe the per-frame position or rotation of components to reproduce the expected animation.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The animation must be long enough to show the complete mechanical chain.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual reference as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task/06_06/06_06.py
+* /xxx/ExeWorldBench/t2/task/06_06/06_06.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t2/task/06_07/06_07.txt

@@ -0,0 +1,75 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+06_07
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/06_07/test_06_07.png
+
+Use only the reference image explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task/06_07
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/06_07. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given a visual reference of a multi-stage mechanical chain.
+
+The visual reference mainly specifies the mechanical components involved and their approximate spatial arrangement, but the exact positions, distances, orientations, and geometric relationships may not directly form an executable mechanical system.
+
+Your task is to reason about how the components should mechanically interact, adjust their spatial configuration when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the static appearance of the reference, but to construct a physically executable mechanical system in which the initial action propagates through all stages and completes the intended chain reaction.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure shown in the reference.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, or other geometric relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- Do not directly prescribe the per-frame position or rotation of components to reproduce the expected animation.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The animation must be long enough to show the complete mechanical chain.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual reference as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task/06_07/06_07.py
+* /xxx/ExeWorldBench/t2/task/06_07/06_07.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t2/task/06_08/06_08.txt

@@ -0,0 +1,75 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+06_08
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/06_08/test_06_08.png
+
+Use only the reference image explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task/06_08
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/06_08. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given a visual reference of a multi-stage mechanical chain.
+
+The visual reference mainly specifies the mechanical components involved and their approximate spatial arrangement, but the exact positions, distances, orientations, and geometric relationships may not directly form an executable mechanical system.
+
+Your task is to reason about how the components should mechanically interact, adjust their spatial configuration when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the static appearance of the reference, but to construct a physically executable mechanical system in which the initial action propagates through all stages and completes the intended chain reaction.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure shown in the reference.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, or other geometric relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- Do not directly prescribe the per-frame position or rotation of components to reproduce the expected animation.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The animation must be long enough to show the complete mechanical chain.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual reference as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task/06_08/06_08.py
+* /xxx/ExeWorldBench/t2/task/06_08/06_08.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t2/task/06_09/06_09.txt

@@ -0,0 +1,75 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+06_09
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/06_09/test_06_09.png
+
+Use only the reference image explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task/06_09
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/06_09. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given a visual reference of a multi-stage mechanical chain.
+
+The visual reference mainly specifies the mechanical components involved and their approximate spatial arrangement, but the exact positions, distances, orientations, and geometric relationships may not directly form an executable mechanical system.
+
+Your task is to reason about how the components should mechanically interact, adjust their spatial configuration when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the static appearance of the reference, but to construct a physically executable mechanical system in which the initial action propagates through all stages and completes the intended chain reaction.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure shown in the reference.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, or other geometric relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- Do not directly prescribe the per-frame position or rotation of components to reproduce the expected animation.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The animation must be long enough to show the complete mechanical chain.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual reference as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task/06_09/06_09.py
+* /xxx/ExeWorldBench/t2/task/06_09/06_09.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t2/task/06_10/06_10.txt

@@ -0,0 +1,75 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+06_10
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/06_10/test_06_10.png
+
+Use only the reference image explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task/06_10
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/06_10. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given a visual reference of a multi-stage mechanical chain.
+
+The visual reference mainly specifies the mechanical components involved and their approximate spatial arrangement, but the exact positions, distances, orientations, and geometric relationships may not directly form an executable mechanical system.
+
+Your task is to reason about how the components should mechanically interact, adjust their spatial configuration when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the static appearance of the reference, but to construct a physically executable mechanical system in which the initial action propagates through all stages and completes the intended chain reaction.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure shown in the reference.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, or other geometric relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- Do not directly prescribe the per-frame position or rotation of components to reproduce the expected animation.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The animation must be long enough to show the complete mechanical chain.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual reference as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task/06_10/06_10.py
+* /xxx/ExeWorldBench/t2/task/06_10/06_10.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t2/task/07_01/07_01.txt

@@ -0,0 +1,75 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+07_01
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/07_01/test_07_01.png
+
+Use only the reference image explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task/07_01
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/07_01. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given a visual reference of a multi-stage mechanical chain.
+
+The visual reference mainly specifies the mechanical components involved and their approximate spatial arrangement, but the exact positions, distances, orientations, and geometric relationships may not directly form an executable mechanical system.
+
+Your task is to reason about how the components should mechanically interact, adjust their spatial configuration when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the static appearance of the reference, but to construct a physically executable mechanical system in which the initial action propagates through all stages and completes the intended chain reaction.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure shown in the reference.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, or other geometric relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- Do not directly prescribe the per-frame position or rotation of components to reproduce the expected animation.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The animation must be long enough to show the complete mechanical chain.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual reference as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task/07_01/07_01.py
+* /xxx/ExeWorldBench/t2/task/07_01/07_01.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t2/task/07_02/07_02.txt

@@ -0,0 +1,75 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+07_02
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/07_02/test_07_02.png
+
+Use only the reference image explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task/07_02
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/07_02. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given a visual reference of a multi-stage mechanical chain.
+
+The visual reference mainly specifies the mechanical components involved and their approximate spatial arrangement, but the exact positions, distances, orientations, and geometric relationships may not directly form an executable mechanical system.
+
+Your task is to reason about how the components should mechanically interact, adjust their spatial configuration when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the static appearance of the reference, but to construct a physically executable mechanical system in which the initial action propagates through all stages and completes the intended chain reaction.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure shown in the reference.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, or other geometric relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- Do not directly prescribe the per-frame position or rotation of components to reproduce the expected animation.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The animation must be long enough to show the complete mechanical chain.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual reference as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task/07_02/07_02.py
+* /xxx/ExeWorldBench/t2/task/07_02/07_02.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t2/task/07_03/07_03.txt

@@ -0,0 +1,75 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+07_03
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/07_03/test_07_03.png
+
+Use only the reference image explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task/07_03
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/07_03. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given a visual reference of a multi-stage mechanical chain.
+
+The visual reference mainly specifies the mechanical components involved and their approximate spatial arrangement, but the exact positions, distances, orientations, and geometric relationships may not directly form an executable mechanical system.
+
+Your task is to reason about how the components should mechanically interact, adjust their spatial configuration when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the static appearance of the reference, but to construct a physically executable mechanical system in which the initial action propagates through all stages and completes the intended chain reaction.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure shown in the reference.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, or other geometric relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- Do not directly prescribe the per-frame position or rotation of components to reproduce the expected animation.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The animation must be long enough to show the complete mechanical chain.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual reference as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task/07_03/07_03.py
+* /xxx/ExeWorldBench/t2/task/07_03/07_03.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t2/task/07_04/07_04.txt

@@ -0,0 +1,75 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+07_04
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/07_04/test_07_04.png
+
+Use only the reference image explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task/07_04
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/07_04. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given a visual reference of a multi-stage mechanical chain.
+
+The visual reference mainly specifies the mechanical components involved and their approximate spatial arrangement, but the exact positions, distances, orientations, and geometric relationships may not directly form an executable mechanical system.
+
+Your task is to reason about how the components should mechanically interact, adjust their spatial configuration when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the static appearance of the reference, but to construct a physically executable mechanical system in which the initial action propagates through all stages and completes the intended chain reaction.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure shown in the reference.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, or other geometric relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- Do not directly prescribe the per-frame position or rotation of components to reproduce the expected animation.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The animation must be long enough to show the complete mechanical chain.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual reference as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task/07_04/07_04.py
+* /xxx/ExeWorldBench/t2/task/07_04/07_04.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.

t2/task/07_05/07_05.txt

@@ -0,0 +1,75 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image, and Blender 5.2.
+
+Complete the task end to end: create and execute the Blender script, inspect and fix the generated result as needed, and save the final artifacts.
+
+Task name:
+07_05
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/07_05/test_07_05.png
+
+Use only the reference image explicitly provided above as reference material. Do not search, scan, inspect, or use any other files or directories as additional reference material.
+
+Output directory:
+/xxx/ExeWorldBench/t2/task/07_05
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/07_05. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given a visual reference of a multi-stage mechanical chain.
+
+The visual reference mainly specifies the mechanical components involved and their approximate spatial arrangement, but the exact positions, distances, orientations, and geometric relationships may not directly form an executable mechanical system.
+
+Your task is to reason about how the components should mechanically interact, adjust their spatial configuration when necessary, and generate a Blender 5.2 Python script that reconstructs and executes the complete mechanical chain in Blender.
+
+The goal is not merely to reproduce the static appearance of the reference, but to construct a physically executable mechanical system in which the initial action propagates through all stages and completes the intended chain reaction.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure shown in the reference.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, or other geometric relationships when necessary.
+- These adjustments must preserve the intended role and interaction of the original components, rather than replacing them with a fundamentally different mechanical solution.
+- The final configuration must allow motion to propagate successfully from the first stage to the final stage through physically plausible mechanical interactions.
+
+2. Physical Motion and No Hard Coding
+
+- The motion of the system must arise from its mechanical structure, physical constraints, contacts, collisions, gravity, and other physically meaningful interactions.
+- Do not directly prescribe the per-frame position or rotation of components to reproduce the expected animation.
+- Do not use teleportation, object replacement, visibility changes, timers, predefined stage schedules, or other scripted shortcuts to fake the mechanical chain.
+- All motion must follow realistic and physically plausible mechanical behavior.
+
+3. Initial Actuation and Causal Propagation
+
+- The initial component or initial stage may already be in motion, or may receive an external force, impulse, torque, or other physical actuation.
+- Except for the initial stage, the motion of downstream components must be naturally caused by the physical outcome of preceding stages. Do not use additional direct control to make downstream components start moving.
+
+4. Complete Chain Execution
+
+- The script must construct the complete mechanical system and produce an animation showing the full chain reaction, rather than only a static scene or a partial subset of stages.
+- The execution must begin from the initial stage, pass through all intended intermediate stages, and ultimately reach the final stage.
+- The animation must be long enough to show the complete mechanical chain.
+- If only part of the chain executes successfully, the implementation is considered incomplete.
+
+5. Scene and Animation
+
+- The initial configuration of the mechanical system must be physically reasonable and serve as a valid starting point for the complete chain reaction.
+- The shapes, overall spatial arrangement, and colors of major components should match the visual reference as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanical system visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+6. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t2/task/07_05/07_05.py
+* /xxx/ExeWorldBench/t2/task/07_05/07_05.blend
+
+The `.py` file must contain the final Blender 5.2 implementation. The `.blend` file must be generated by executing this final script and must contain the complete mechanical device and its full animation.