diff --git a/t2/task/04_10/test_04_10.png b/t2/task/04_10/test_04_10.png
new file mode 100644
index 0000000000000000000000000000000000000000..79531bf2dd6acfe0c6379a3534b111cc87706692
--- /dev/null
+++ b/t2/task/04_10/test_04_10.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5868b22729aa37b434e0260b4fd6d8ab0cc05a4a3b1ddafa8d64ada05b1487aa
+size 14388
diff --git a/t2/task/05_01/05_01.txt b/t2/task/05_01/05_01.txt
new file mode 100644
index 0000000000000000000000000000000000000000..9fc802f1825bd3c2226cb551fd67fc1cc144b2fd
--- /dev/null
+++ b/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.
diff --git a/t2/task/05_01/test_05_01.png b/t2/task/05_01/test_05_01.png
new file mode 100644
index 0000000000000000000000000000000000000000..6b9b211098360f4e693d2d524853483c12db09d2
--- /dev/null
+++ b/t2/task/05_01/test_05_01.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eb8c0f4c15f9a8aa340d88432952df6af4b6a0fd4be4c8d1ff8881541238567b
+size 15021
diff --git a/t2/task/05_02/05_02.txt b/t2/task/05_02/05_02.txt
new file mode 100644
index 0000000000000000000000000000000000000000..ce7e867b55019ad4c39f44e075eb137dd09a09e1
--- /dev/null
+++ b/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.
diff --git a/t2/task/05_02/test_05_02.png b/t2/task/05_02/test_05_02.png
new file mode 100644
index 0000000000000000000000000000000000000000..884a9f1d51e42767f899f1e922a4c956a7787193
--- /dev/null
+++ b/t2/task/05_02/test_05_02.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b4c1c8f28401613df97ef8c93feb8ac7df4782ee18b6f2cd665c063dfa718170
+size 15785
diff --git a/t2/task/05_03/05_03.txt b/t2/task/05_03/05_03.txt
new file mode 100644
index 0000000000000000000000000000000000000000..33f619f5d2ba8440ad8024655583440f0dd45d77
--- /dev/null
+++ b/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.
diff --git a/t2/task/05_03/test_05_03.png b/t2/task/05_03/test_05_03.png
new file mode 100644
index 0000000000000000000000000000000000000000..04d6c79d799e4f1972dfac9d04e75bf7cd63a501
--- /dev/null
+++ b/t2/task/05_03/test_05_03.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fda35e7a2892d15fd62ab6725580e2293e3a1a3df4c8a488fac0c40ab517ae17
+size 16428
diff --git a/t2/task/05_04/05_04.txt b/t2/task/05_04/05_04.txt
new file mode 100644
index 0000000000000000000000000000000000000000..005baa7bdb2d11604831bb2bb32789335dd94f73
--- /dev/null
+++ b/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.
diff --git a/t2/task/05_04/test_05_04.png b/t2/task/05_04/test_05_04.png
new file mode 100644
index 0000000000000000000000000000000000000000..178817c154a6e04fb7d14b8ec034d19c04b6d738
--- /dev/null
+++ b/t2/task/05_04/test_05_04.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b59bd326b48067a4a53fd9e5b1cadffcb3a4c9f27ed63fadebc4ca1a8be98645
+size 15551
diff --git a/t2/task/05_05/05_05.txt b/t2/task/05_05/05_05.txt
new file mode 100644
index 0000000000000000000000000000000000000000..3dfd68ac8ab13a6325b29d2ca75d1fa3e3716259
--- /dev/null
+++ b/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.
diff --git a/t2/task/05_05/test_05_05.png b/t2/task/05_05/test_05_05.png
new file mode 100644
index 0000000000000000000000000000000000000000..058923f6d9403becddf7c4d0f5bd36dd3a809bf6
--- /dev/null
+++ b/t2/task/05_05/test_05_05.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d9f1b78d5ec2446a50a38c5fa69fc2d1abf2f12a3e1fdf82f8821573e40f6067
+size 14695
diff --git a/t2/task/05_06/05_06.txt b/t2/task/05_06/05_06.txt
new file mode 100644
index 0000000000000000000000000000000000000000..60667a38be1cd3a414b8de0ec8ce35dcb8e0f03a
--- /dev/null
+++ b/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.
diff --git a/t2/task/05_06/test_05_06.png b/t2/task/05_06/test_05_06.png
new file mode 100644
index 0000000000000000000000000000000000000000..c5cf034a20d0c5b838802a8a1461151df6c7cf68
--- /dev/null
+++ b/t2/task/05_06/test_05_06.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c0fe181ca6d33c12adae6557233ea4dd35576a6902bddd995aac4f084e37e8f7
+size 15372
diff --git a/t2/task/05_07/05_07.txt b/t2/task/05_07/05_07.txt
new file mode 100644
index 0000000000000000000000000000000000000000..f1c267f5eb245cf00e5f801fc52e13c78398bcb6
--- /dev/null
+++ b/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.
diff --git a/t2/task/05_07/test_05_07.png b/t2/task/05_07/test_05_07.png
new file mode 100644
index 0000000000000000000000000000000000000000..cef93c1f565a49bbbb9fd0b729319154a2f8df1a
--- /dev/null
+++ b/t2/task/05_07/test_05_07.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:385cc0eb00f94d3b0ee09eac42617bf79b43f574106a36e952b00417208efe8a
+size 15899
diff --git a/t2/task/05_08/05_08.txt b/t2/task/05_08/05_08.txt
new file mode 100644
index 0000000000000000000000000000000000000000..cc9fcd73cb4429d5b6c20f4339d409e37cfbc5a5
--- /dev/null
+++ b/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.
diff --git a/t2/task/05_08/test_05_08.png b/t2/task/05_08/test_05_08.png
new file mode 100644
index 0000000000000000000000000000000000000000..7a1a44177d8e1d29a40236eb48870cb8e6921ae2
--- /dev/null
+++ b/t2/task/05_08/test_05_08.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bcce90215b637cb30eb4dbba31cb2540a83a77308eebf8900799736ff01e3ad4
+size 14827
diff --git a/t2/task/05_09/05_09.txt b/t2/task/05_09/05_09.txt
new file mode 100644
index 0000000000000000000000000000000000000000..2136c4ab6582cb87ac97a25d995c582f2462f162
--- /dev/null
+++ b/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.
diff --git a/t2/task/05_09/test_05_09.png b/t2/task/05_09/test_05_09.png
new file mode 100644
index 0000000000000000000000000000000000000000..3f356e3792dcc92e2c5cd9cdc5f28ba324e72bbe
--- /dev/null
+++ b/t2/task/05_09/test_05_09.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f287a0faebbe926d38aba367ce628aabe19873596ff19a533229747b5cde28f9
+size 16469
diff --git a/t2/task/05_10/05_10.txt b/t2/task/05_10/05_10.txt
new file mode 100644
index 0000000000000000000000000000000000000000..9cbfc7bcee2a62c1b8460759a8338f36e121bc6b
--- /dev/null
+++ b/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.
diff --git a/t2/task/05_10/test_05_10.png b/t2/task/05_10/test_05_10.png
new file mode 100644
index 0000000000000000000000000000000000000000..4aa050d1743304ea027ef7419d5d4fa24aa40b61
--- /dev/null
+++ b/t2/task/05_10/test_05_10.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a37b2d96ed4a450e322234127ae48677d05105291f7f767826f8623061ea79a3
+size 14382
diff --git a/t2/task/06_01/06_01.txt b/t2/task/06_01/06_01.txt
new file mode 100644
index 0000000000000000000000000000000000000000..a5103a7b98f1d4d3755162555c6b130ebbb05505
--- /dev/null
+++ b/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.
diff --git a/t2/task/06_01/test_06_01.png b/t2/task/06_01/test_06_01.png
new file mode 100644
index 0000000000000000000000000000000000000000..094f3934f3407cbfb0d85478a23ec4261294cf48
--- /dev/null
+++ b/t2/task/06_01/test_06_01.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2bed952a1139c43fd90d0e018835ae8e174e55241b4cf7020ce10875ba0b43d5
+size 19309
diff --git a/t2/task/06_02/06_02.txt b/t2/task/06_02/06_02.txt
new file mode 100644
index 0000000000000000000000000000000000000000..6eb72f4febadd2493ee95087cd885630642fbdbf
--- /dev/null
+++ b/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.
diff --git a/t2/task/06_02/test_06_02.png b/t2/task/06_02/test_06_02.png
new file mode 100644
index 0000000000000000000000000000000000000000..9490b262d953d5b64466532cd769dc6e5eac3aa6
--- /dev/null
+++ b/t2/task/06_02/test_06_02.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3d5e5456f131d63318e63a1b5caa445d9d28f3c2aa5d23665671ee011c12ea7c
+size 16133
diff --git a/t2/task/06_03/06_03.txt b/t2/task/06_03/06_03.txt
new file mode 100644
index 0000000000000000000000000000000000000000..005b8b5b06590f093f4b331fef16a1c1ba616965
--- /dev/null
+++ b/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.
diff --git a/t2/task/06_03/test_06_03.png b/t2/task/06_03/test_06_03.png
new file mode 100644
index 0000000000000000000000000000000000000000..1b25d8a7697249fddacf1d73a750b7ca3a78efd9
--- /dev/null
+++ b/t2/task/06_03/test_06_03.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:06f6bc8ed4ee8b4fb28cd1c3a256741a18a581f33cda1f5e80705ee4572abbc9
+size 17104
diff --git a/t2/task/06_04/06_04.txt b/t2/task/06_04/06_04.txt
new file mode 100644
index 0000000000000000000000000000000000000000..68ee5701d17f822033f146c37a4b9f31d6c93aba
--- /dev/null
+++ b/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.
diff --git a/t2/task/06_04/test_06_04.png b/t2/task/06_04/test_06_04.png
new file mode 100644
index 0000000000000000000000000000000000000000..d9702604598d328972832e4de0fc36938c26249a
--- /dev/null
+++ b/t2/task/06_04/test_06_04.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e3f3066f0287a8114174ff6fbb9acda974fea9a87cdcfd3d88a291a6768ede3f
+size 16160
diff --git a/t2/task/06_05/06_05.txt b/t2/task/06_05/06_05.txt
new file mode 100644
index 0000000000000000000000000000000000000000..ec28990f5d217ac4ec22380ebfa615292c9a01ca
--- /dev/null
+++ b/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.
diff --git a/t2/task/06_05/test_06_05.png b/t2/task/06_05/test_06_05.png
new file mode 100644
index 0000000000000000000000000000000000000000..d03c4852e2d0abe72bb0debe174ac0b566251c4d
--- /dev/null
+++ b/t2/task/06_05/test_06_05.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3d1c4bf70468b5feb8b3b6f02d78d2c0d4ea47bab9bfd68fd0cfb309de1f69cb
+size 15506
diff --git a/t2/task/06_06/06_06.txt b/t2/task/06_06/06_06.txt
new file mode 100644
index 0000000000000000000000000000000000000000..1376c40d7d62c21f1f6a3c1ec3c06bd4834de512
--- /dev/null
+++ b/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.
diff --git a/t2/task/06_06/test_06_06.png b/t2/task/06_06/test_06_06.png
new file mode 100644
index 0000000000000000000000000000000000000000..b1c05dddac46c4522fd47412ad95244864c8afeb
--- /dev/null
+++ b/t2/task/06_06/test_06_06.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7c4b7aab41686224670f9b2fac03821f66c9cfe792afa7690bcc43b26960ad26
+size 14999
diff --git a/t2/task/06_07/06_07.txt b/t2/task/06_07/06_07.txt
new file mode 100644
index 0000000000000000000000000000000000000000..18ba02d9d6049099b9d21f65a60d1f7660626f7f
--- /dev/null
+++ b/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.
diff --git a/t2/task/06_07/test_06_07.png b/t2/task/06_07/test_06_07.png
new file mode 100644
index 0000000000000000000000000000000000000000..7ccc11e6cd9ba3c79bbf89dbcb5313725d770bc3
--- /dev/null
+++ b/t2/task/06_07/test_06_07.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f34ebd50592dc66cd5181ac003bb4c5335cf933c1adab1b4ca570119426c5dee
+size 15373
diff --git a/t2/task/06_08/06_08.txt b/t2/task/06_08/06_08.txt
new file mode 100644
index 0000000000000000000000000000000000000000..f5c566820bfc1f7c4e048efd90bafd3bd881a4e6
--- /dev/null
+++ b/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.
diff --git a/t2/task/06_08/test_06_08.png b/t2/task/06_08/test_06_08.png
new file mode 100644
index 0000000000000000000000000000000000000000..dbc6ca92e3c84649f38e0d9c7f6dbcec66fd1fbb
--- /dev/null
+++ b/t2/task/06_08/test_06_08.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cb370e0c1fead183a4fde3b954893f2bfb8609abb40f3f98a801d7a720df8be7
+size 16330
diff --git a/t2/task/06_09/06_09.txt b/t2/task/06_09/06_09.txt
new file mode 100644
index 0000000000000000000000000000000000000000..80d99fe639b399fd18a5823fe52dce1c94e4130a
--- /dev/null
+++ b/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.
diff --git a/t2/task/06_09/test_06_09.png b/t2/task/06_09/test_06_09.png
new file mode 100644
index 0000000000000000000000000000000000000000..598d7c5bb20ea081e8897785530de45255794dcb
--- /dev/null
+++ b/t2/task/06_09/test_06_09.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a5726ec6d7f1c457ba42f6231ef0d26e4cae5c3c6865694a4416e09cfb41222c
+size 16214
diff --git a/t2/task/06_10/06_10.txt b/t2/task/06_10/06_10.txt
new file mode 100644
index 0000000000000000000000000000000000000000..3018e0219aae08351da5850c0ffb8397628d9357
--- /dev/null
+++ b/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.
diff --git a/t2/task/06_10/test_06_10.png b/t2/task/06_10/test_06_10.png
new file mode 100644
index 0000000000000000000000000000000000000000..c7df37d8fb776f8beed4999f45633788816b5325
--- /dev/null
+++ b/t2/task/06_10/test_06_10.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4319290bce3e282dd716e4b0b92453cb34198596c36aab7d815cafd171be2393
+size 16485
diff --git a/t2/task/07_01/07_01.txt b/t2/task/07_01/07_01.txt
new file mode 100644
index 0000000000000000000000000000000000000000..bcd7144b108313af28065b1f72db5cad0e79e4db
--- /dev/null
+++ b/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.
diff --git a/t2/task/07_01/test_07_01.png b/t2/task/07_01/test_07_01.png
new file mode 100644
index 0000000000000000000000000000000000000000..84aeadd1164281485d6c4e23c4f2207abd77b710
--- /dev/null
+++ b/t2/task/07_01/test_07_01.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ee88983ad55e8e29ca9f6228479822fe398bb783842f0ca01be817cd61d9eac1
+size 17586
diff --git a/t2/task/07_02/07_02.txt b/t2/task/07_02/07_02.txt
new file mode 100644
index 0000000000000000000000000000000000000000..ae27cc0065654a66b096d035066e63dca2c66e0a
--- /dev/null
+++ b/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.
diff --git a/t2/task/07_02/test_07_02.png b/t2/task/07_02/test_07_02.png
new file mode 100644
index 0000000000000000000000000000000000000000..f8d6c4a01e2553c144e2761844696266e65ece71
--- /dev/null
+++ b/t2/task/07_02/test_07_02.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fe05f3d34752ee6bc08d822fdc200ffd652058a7e85457bdc434a4468ec4d13c
+size 16354
diff --git a/t2/task/07_03/07_03.txt b/t2/task/07_03/07_03.txt
new file mode 100644
index 0000000000000000000000000000000000000000..0c7d8a89c2706b8382531e565422f7379762f50e
--- /dev/null
+++ b/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.
diff --git a/t2/task/07_03/test_07_03.png b/t2/task/07_03/test_07_03.png
new file mode 100644
index 0000000000000000000000000000000000000000..b7230e4a096920fc2eaebd74ce7a5b4e8b8b4c36
--- /dev/null
+++ b/t2/task/07_03/test_07_03.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cfd66b0f0a2273b90b5b6e963ea0ca60a6c9a613f3e1f17bf002c92fbce1b8b3
+size 17151
diff --git a/t2/task/07_04/07_04.txt b/t2/task/07_04/07_04.txt
new file mode 100644
index 0000000000000000000000000000000000000000..92a168735cb24c708beffb560ed61a605762ad97
--- /dev/null
+++ b/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.
diff --git a/t2/task/07_04/test_07_04.png b/t2/task/07_04/test_07_04.png
new file mode 100644
index 0000000000000000000000000000000000000000..72deba10b6efe1adda4410d7db21457dfdf3bf2f
--- /dev/null
+++ b/t2/task/07_04/test_07_04.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:273510d9e34b00dc7bb697ae0fdaeb55533b6332ee3281c1044c98314ae4ed2f
+size 17086
diff --git a/t2/task/07_05/07_05.txt b/t2/task/07_05/07_05.txt
new file mode 100644
index 0000000000000000000000000000000000000000..af6ff55cce45a7894592e2748400cd3e99d4d158
--- /dev/null
+++ b/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.
diff --git a/t2/task/07_05/test_07_05.png b/t2/task/07_05/test_07_05.png
new file mode 100644
index 0000000000000000000000000000000000000000..eaee19455767230e1a2f837e6ef0c3a3a1dd1e98
--- /dev/null
+++ b/t2/task/07_05/test_07_05.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:de0db6582fb2ac3fb4fe7c7852bde8b1bb6271723e4c30976d2dbdf6d8892713
+size 16166
diff --git a/t2/task/07_06/07_06.txt b/t2/task/07_06/07_06.txt
new file mode 100644
index 0000000000000000000000000000000000000000..7017667fb95ceb60d52bcee9a67d00753117aeb7
--- /dev/null
+++ b/t2/task/07_06/07_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:
+07_06
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/07_06/test_07_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/07_06
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/07_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/07_06/07_06.py
+* /xxx/ExeWorldBench/t2/task/07_06/07_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.
diff --git a/t2/task/07_06/test_07_06.png b/t2/task/07_06/test_07_06.png
new file mode 100644
index 0000000000000000000000000000000000000000..dd8ba0fddde983ebea507ea07f4c629a6671b397
--- /dev/null
+++ b/t2/task/07_06/test_07_06.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5c8c944f78d153a69947c2c7bb970473d3564d99ff5f58389c747e781c09c502
+size 15927
diff --git a/t2/task/07_07/07_07.txt b/t2/task/07_07/07_07.txt
new file mode 100644
index 0000000000000000000000000000000000000000..49e3882c0fc05f0e48d7742a88b930d742ce87ad
--- /dev/null
+++ b/t2/task/07_07/07_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:
+07_07
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/07_07/test_07_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/07_07
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/07_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/07_07/07_07.py
+* /xxx/ExeWorldBench/t2/task/07_07/07_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.
diff --git a/t2/task/07_07/test_07_07.png b/t2/task/07_07/test_07_07.png
new file mode 100644
index 0000000000000000000000000000000000000000..64d4edf318504c522693175ccb46daab5438e70d
--- /dev/null
+++ b/t2/task/07_07/test_07_07.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f08706c7e9e5496791d2411baeeb484f04dfd662f3d5bad8484b2ff1553b9adc
+size 15664
diff --git a/t2/task/07_08/07_08.txt b/t2/task/07_08/07_08.txt
new file mode 100644
index 0000000000000000000000000000000000000000..111eed66107fb5b693ebe9d3bca25d75ce09b467
--- /dev/null
+++ b/t2/task/07_08/07_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:
+07_08
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/07_08/test_07_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/07_08
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/07_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/07_08/07_08.py
+* /xxx/ExeWorldBench/t2/task/07_08/07_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.
diff --git a/t2/task/07_08/test_07_08.png b/t2/task/07_08/test_07_08.png
new file mode 100644
index 0000000000000000000000000000000000000000..5655af8a0ae43249e7294c64dcc878b3a6342d3c
--- /dev/null
+++ b/t2/task/07_08/test_07_08.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:39dd894a02babe0de6a58d079acc582135804e24c31060776f859882d3051ba0
+size 16419
diff --git a/t2/task/07_09/07_09.txt b/t2/task/07_09/07_09.txt
new file mode 100644
index 0000000000000000000000000000000000000000..821ea6f42efa17561e195432ddd8661a07681800
--- /dev/null
+++ b/t2/task/07_09/07_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:
+07_09
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/07_09/test_07_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/07_09
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/07_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/07_09/07_09.py
+* /xxx/ExeWorldBench/t2/task/07_09/07_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.
diff --git a/t2/task/07_09/test_07_09.png b/t2/task/07_09/test_07_09.png
new file mode 100644
index 0000000000000000000000000000000000000000..37a15925cd4113f4845db00c3d7af5a70fbec57d
--- /dev/null
+++ b/t2/task/07_09/test_07_09.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:871fa9b69f5715eb8b7266b8af9b79c47bc19b97f57d77fa7f3ed325afe654ac
+size 17131
diff --git a/t2/task/07_10/07_10.txt b/t2/task/07_10/07_10.txt
new file mode 100644
index 0000000000000000000000000000000000000000..6dc38626e568888a73c08630c6f4599d6d68481b
--- /dev/null
+++ b/t2/task/07_10/07_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:
+07_10
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/07_10/test_07_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/07_10
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/07_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/07_10/07_10.py
+* /xxx/ExeWorldBench/t2/task/07_10/07_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.
diff --git a/t2/task/07_10/test_07_10.png b/t2/task/07_10/test_07_10.png
new file mode 100644
index 0000000000000000000000000000000000000000..0751988b57e6e814c9523ddea272eba3c728f144
--- /dev/null
+++ b/t2/task/07_10/test_07_10.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0ebdeee73ad727f02e41f3d8b55235e0dd0a6739a7866bdb0ef13c59c34fc3c3
+size 16940
diff --git a/t2/task/08_01/08_01.txt b/t2/task/08_01/08_01.txt
new file mode 100644
index 0000000000000000000000000000000000000000..092d71cfcd31d76fc5a6ff13685727c4a61b90a4
--- /dev/null
+++ b/t2/task/08_01/08_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:
+08_01
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/08_01/test_08_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/08_01
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/08_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/08_01/08_01.py
+* /xxx/ExeWorldBench/t2/task/08_01/08_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.
diff --git a/t2/task/08_01/test_08_01.png b/t2/task/08_01/test_08_01.png
new file mode 100644
index 0000000000000000000000000000000000000000..b39c4a9f9070c17bfbf7ee744d93727066a51eaf
--- /dev/null
+++ b/t2/task/08_01/test_08_01.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:79c690aaa36e2aed02a391891add31a858dfee973a2c4a366340f4ecf4af24ba
+size 17554
diff --git a/t2/task/08_02/08_02.txt b/t2/task/08_02/08_02.txt
new file mode 100644
index 0000000000000000000000000000000000000000..5e5bfed2e658dd551ae3c07eea31a16f8b2fa573
--- /dev/null
+++ b/t2/task/08_02/08_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:
+08_02
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/08_02/test_08_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/08_02
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/08_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/08_02/08_02.py
+* /xxx/ExeWorldBench/t2/task/08_02/08_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.
diff --git a/t2/task/08_02/test_08_02.png b/t2/task/08_02/test_08_02.png
new file mode 100644
index 0000000000000000000000000000000000000000..7bcdcaec515db2cd4c7f50301b9f64a3a0fdae6f
--- /dev/null
+++ b/t2/task/08_02/test_08_02.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cf08fd2a7d639c946cc52bd43738323aa5364ec38a22ced28ba08d3935a726f6
+size 16176
diff --git a/t2/task/08_03/08_03.txt b/t2/task/08_03/08_03.txt
new file mode 100644
index 0000000000000000000000000000000000000000..69a50890b13c0a94d2bc855ac4fe016d79ff6c78
--- /dev/null
+++ b/t2/task/08_03/08_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:
+08_03
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/08_03/test_08_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/08_03
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/08_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/08_03/08_03.py
+* /xxx/ExeWorldBench/t2/task/08_03/08_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.
diff --git a/t2/task/08_03/test_08_03.png b/t2/task/08_03/test_08_03.png
new file mode 100644
index 0000000000000000000000000000000000000000..6002437ee8912ff2cca7bcae76a6eb4a6e566e66
--- /dev/null
+++ b/t2/task/08_03/test_08_03.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:647553d74ccc5e77ead4a75ab2b207004573ba70385a1dedc11403312986b818
+size 17076
diff --git a/t2/task/08_04/08_04.txt b/t2/task/08_04/08_04.txt
new file mode 100644
index 0000000000000000000000000000000000000000..50d145cc281bf43195639c853c40ab3df1f64e4c
--- /dev/null
+++ b/t2/task/08_04/08_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:
+08_04
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/08_04/test_08_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/08_04
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/08_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/08_04/08_04.py
+* /xxx/ExeWorldBench/t2/task/08_04/08_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.
diff --git a/t2/task/08_04/test_08_04.png b/t2/task/08_04/test_08_04.png
new file mode 100644
index 0000000000000000000000000000000000000000..d6368fdee08c3f90e65881a08f3d202d3b9083d5
--- /dev/null
+++ b/t2/task/08_04/test_08_04.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e83609fdd8eaf9a536c325f58fac112ce8d07ab5fe4ff3f4ba3952c44f2c09d9
+size 18147
diff --git a/t2/task/08_05/08_05.txt b/t2/task/08_05/08_05.txt
new file mode 100644
index 0000000000000000000000000000000000000000..9b5d569d15a90c1597b97d991aed8a6bbbfd9dfb
--- /dev/null
+++ b/t2/task/08_05/08_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:
+08_05
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/08_05/test_08_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/08_05
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/08_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/08_05/08_05.py
+* /xxx/ExeWorldBench/t2/task/08_05/08_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.
diff --git a/t2/task/08_05/test_08_05.png b/t2/task/08_05/test_08_05.png
new file mode 100644
index 0000000000000000000000000000000000000000..40e8c98f2fbe57eb524f722100bec88655358703
--- /dev/null
+++ b/t2/task/08_05/test_08_05.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:86dbd9ea4f8000931f9c45ce6f5e4755f383b94a9b01316ed788429c6622ce63
+size 17986
diff --git a/t2/task/08_06/08_06.txt b/t2/task/08_06/08_06.txt
new file mode 100644
index 0000000000000000000000000000000000000000..a70536025640edcaae424fb32b1ab5320d728763
--- /dev/null
+++ b/t2/task/08_06/08_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:
+08_06
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/08_06/test_08_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/08_06
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/08_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/08_06/08_06.py
+* /xxx/ExeWorldBench/t2/task/08_06/08_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.
diff --git a/t2/task/08_06/test_08_06.png b/t2/task/08_06/test_08_06.png
new file mode 100644
index 0000000000000000000000000000000000000000..8b29046f7ba937cfa650a07b8b413d46415b043e
--- /dev/null
+++ b/t2/task/08_06/test_08_06.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3e09e4a57353f07574c6e44b6451f12b4a7c01ac2a98bb7ec56dda521cb1e2b4
+size 16814
diff --git a/t2/task/08_07/08_07.txt b/t2/task/08_07/08_07.txt
new file mode 100644
index 0000000000000000000000000000000000000000..b362974c904577f3050f63d2685fc04492d3f12e
--- /dev/null
+++ b/t2/task/08_07/08_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:
+08_07
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/08_07/test_08_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/08_07
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/08_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/08_07/08_07.py
+* /xxx/ExeWorldBench/t2/task/08_07/08_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.
diff --git a/t2/task/08_07/test_08_07.png b/t2/task/08_07/test_08_07.png
new file mode 100644
index 0000000000000000000000000000000000000000..62aa9f11b63851f1fa988d2f78e6a71129473570
--- /dev/null
+++ b/t2/task/08_07/test_08_07.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:62f73a18b514474f3d8a2d5e6820bf61cdda5bd0fba39ee41393f9f573656973
+size 17268
diff --git a/t2/task/08_08/08_08.txt b/t2/task/08_08/08_08.txt
new file mode 100644
index 0000000000000000000000000000000000000000..22670b70b47ddcfe58c2fe3a5a0b8898f647c223
--- /dev/null
+++ b/t2/task/08_08/08_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:
+08_08
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/08_08/test_08_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/08_08
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/08_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/08_08/08_08.py
+* /xxx/ExeWorldBench/t2/task/08_08/08_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.
diff --git a/t2/task/08_08/test_08_08.png b/t2/task/08_08/test_08_08.png
new file mode 100644
index 0000000000000000000000000000000000000000..07666e15b46ca065d54510541297c0114b2015fa
--- /dev/null
+++ b/t2/task/08_08/test_08_08.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:083fcfb1ee2ac8f225fba594fd49d0ed6961f8b7b1b0b041eae933e6564ac045
+size 18343
diff --git a/t2/task/08_09/08_09.txt b/t2/task/08_09/08_09.txt
new file mode 100644
index 0000000000000000000000000000000000000000..71f6702638992761dc9c7809e6b4af1141cd415f
--- /dev/null
+++ b/t2/task/08_09/08_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:
+08_09
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/08_09/test_08_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/08_09
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/08_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/08_09/08_09.py
+* /xxx/ExeWorldBench/t2/task/08_09/08_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.
diff --git a/t2/task/08_09/test_08_09.png b/t2/task/08_09/test_08_09.png
new file mode 100644
index 0000000000000000000000000000000000000000..75b8990621e8f2a2fa2ea443a8edb7fe607beb00
--- /dev/null
+++ b/t2/task/08_09/test_08_09.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1702503e92b2d5757e03e6cdb1a5fc2cb09f0f0df6d92730958ed1ec3d8f0218
+size 18222
diff --git a/t2/task/08_10/08_10.txt b/t2/task/08_10/08_10.txt
new file mode 100644
index 0000000000000000000000000000000000000000..e9e24269d564a88027fcc588654f8fc6873c61d5
--- /dev/null
+++ b/t2/task/08_10/08_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:
+08_10
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/08_10/test_08_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/08_10
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/08_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/08_10/08_10.py
+* /xxx/ExeWorldBench/t2/task/08_10/08_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.
diff --git a/t2/task/08_10/test_08_10.png b/t2/task/08_10/test_08_10.png
new file mode 100644
index 0000000000000000000000000000000000000000..773ba44bb2efabc85a44c3b406de35e1981747c1
--- /dev/null
+++ b/t2/task/08_10/test_08_10.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1701c35b7c190ddfd6076dac8fcd09602620136a95b2b72e492272c297dd42ad
+size 16830
diff --git a/t2/task/09_01/09_01.txt b/t2/task/09_01/09_01.txt
new file mode 100644
index 0000000000000000000000000000000000000000..36c43211aa380c97b851be44ca74ebcb83fee499
--- /dev/null
+++ b/t2/task/09_01/09_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:
+09_01
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/09_01/test_09_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/09_01
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/09_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/09_01/09_01.py
+* /xxx/ExeWorldBench/t2/task/09_01/09_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.
diff --git a/t2/task/09_01/test_09_01.png b/t2/task/09_01/test_09_01.png
new file mode 100644
index 0000000000000000000000000000000000000000..3f8527fc1139874017a9e05dce6a211e2eb4460a
--- /dev/null
+++ b/t2/task/09_01/test_09_01.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a20177befdd3e87993c2b5bf2159c5cd7facb4094335b2d0b6b75c061acf1fd7
+size 18915
diff --git a/t2/task/09_02/09_02.txt b/t2/task/09_02/09_02.txt
new file mode 100644
index 0000000000000000000000000000000000000000..9ca2aa59e105240fb779047106a8ddd347a3579a
--- /dev/null
+++ b/t2/task/09_02/09_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:
+09_02
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/09_02/test_09_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/09_02
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/09_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/09_02/09_02.py
+* /xxx/ExeWorldBench/t2/task/09_02/09_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.
diff --git a/t2/task/09_02/test_09_02.png b/t2/task/09_02/test_09_02.png
new file mode 100644
index 0000000000000000000000000000000000000000..432981aa32fb650a766bc71cdf02a501af2f9322
--- /dev/null
+++ b/t2/task/09_02/test_09_02.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:875a760aace51e5b90621f1dde2cbaad574b1b4e4cc253839644c7a264176520
+size 17296
diff --git a/t2/task/09_03/09_03.txt b/t2/task/09_03/09_03.txt
new file mode 100644
index 0000000000000000000000000000000000000000..b9dbab682faa7791147a04103abfa9961637fd6d
--- /dev/null
+++ b/t2/task/09_03/09_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:
+09_03
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/09_03/test_09_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/09_03
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/09_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/09_03/09_03.py
+* /xxx/ExeWorldBench/t2/task/09_03/09_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.
diff --git a/t2/task/09_03/test_09_03.png b/t2/task/09_03/test_09_03.png
new file mode 100644
index 0000000000000000000000000000000000000000..fe00a45109b68eba08c4ed5d550483faba85eac0
--- /dev/null
+++ b/t2/task/09_03/test_09_03.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c82e938807a7c29b0d142166bf2921a27ac79201f27a7a5f8c55d58760adb9b4
+size 18084
diff --git a/t2/task/09_04/09_04.txt b/t2/task/09_04/09_04.txt
new file mode 100644
index 0000000000000000000000000000000000000000..1f10170a37df25b51d4871fd9a6db78baf3cb441
--- /dev/null
+++ b/t2/task/09_04/09_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:
+09_04
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/09_04/test_09_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/09_04
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/09_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/09_04/09_04.py
+* /xxx/ExeWorldBench/t2/task/09_04/09_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.
diff --git a/t2/task/09_04/test_09_04.png b/t2/task/09_04/test_09_04.png
new file mode 100644
index 0000000000000000000000000000000000000000..98bc711bf567991e692ab09e559015188200e26d
--- /dev/null
+++ b/t2/task/09_04/test_09_04.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8e3a3eb0491c66f5e5796b24ca6dfd2b4bd1bc805fa9ef3756033638599c9d09
+size 18816
diff --git a/t2/task/09_05/09_05.txt b/t2/task/09_05/09_05.txt
new file mode 100644
index 0000000000000000000000000000000000000000..557865abafca7b3c5af2c52a2a35073e75ee981e
--- /dev/null
+++ b/t2/task/09_05/09_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:
+09_05
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/09_05/test_09_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/09_05
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/09_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/09_05/09_05.py
+* /xxx/ExeWorldBench/t2/task/09_05/09_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.
diff --git a/t2/task/09_05/test_09_05.png b/t2/task/09_05/test_09_05.png
new file mode 100644
index 0000000000000000000000000000000000000000..6235fe55809309f192c00397b946c82562afa99c
--- /dev/null
+++ b/t2/task/09_05/test_09_05.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f4271bd96099c7791296e274cb3e7084a3e4be44aaef1ee95974465737e4d019
+size 17958
diff --git a/t2/task/09_06/09_06.txt b/t2/task/09_06/09_06.txt
new file mode 100644
index 0000000000000000000000000000000000000000..da4a4df36e08f31f85e0c891be13a27144399ca5
--- /dev/null
+++ b/t2/task/09_06/09_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:
+09_06
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/09_06/test_09_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/09_06
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/09_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/09_06/09_06.py
+* /xxx/ExeWorldBench/t2/task/09_06/09_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.
diff --git a/t2/task/09_06/test_09_06.png b/t2/task/09_06/test_09_06.png
new file mode 100644
index 0000000000000000000000000000000000000000..705158bc6b3cc1903b0eb7715c0c01f974e7fa8a
--- /dev/null
+++ b/t2/task/09_06/test_09_06.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7bbde386fe0755e31ddf1ad78afb855356f3df6fa299711a31f9c361dc9f6859
+size 18313
diff --git a/t2/task/09_07/09_07.txt b/t2/task/09_07/09_07.txt
new file mode 100644
index 0000000000000000000000000000000000000000..26edb4d191a67a1add8cad332fb2d1d04a528987
--- /dev/null
+++ b/t2/task/09_07/09_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:
+09_07
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/09_07/test_09_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/09_07
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/09_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/09_07/09_07.py
+* /xxx/ExeWorldBench/t2/task/09_07/09_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.
diff --git a/t2/task/09_07/test_09_07.png b/t2/task/09_07/test_09_07.png
new file mode 100644
index 0000000000000000000000000000000000000000..c664e0a5bbf953a50be4ee891ae9e284bee53fa5
--- /dev/null
+++ b/t2/task/09_07/test_09_07.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8083211b0e06783a4f9cbee6758c1c666b3a7fc328c2321d46ea837680043ce8
+size 17122
diff --git a/t2/task/09_08/09_08.txt b/t2/task/09_08/09_08.txt
new file mode 100644
index 0000000000000000000000000000000000000000..8a9b84f5f135867172345150022310d9b936682c
--- /dev/null
+++ b/t2/task/09_08/09_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:
+09_08
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/09_08/test_09_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/09_08
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/09_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/09_08/09_08.py
+* /xxx/ExeWorldBench/t2/task/09_08/09_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.
diff --git a/t2/task/09_08/test_09_08.png b/t2/task/09_08/test_09_08.png
new file mode 100644
index 0000000000000000000000000000000000000000..fdc5f05ed7da862028f18580c6fa8f96be5dd4cf
--- /dev/null
+++ b/t2/task/09_08/test_09_08.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e46bba7afa84e4d12a993782b540c344ec983350472e46c8e4ba55224004b313
+size 17210
diff --git a/t2/task/09_09/09_09.txt b/t2/task/09_09/09_09.txt
new file mode 100644
index 0000000000000000000000000000000000000000..a0e002503841f5d64929846f84d3c79b420fe5ee
--- /dev/null
+++ b/t2/task/09_09/09_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:
+09_09
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/09_09/test_09_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/09_09
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/09_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/09_09/09_09.py
+* /xxx/ExeWorldBench/t2/task/09_09/09_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.
diff --git a/t2/task/09_09/test_09_09.png b/t2/task/09_09/test_09_09.png
new file mode 100644
index 0000000000000000000000000000000000000000..0a59cb7f2e95817cc09537a48c841d85d8b99fad
--- /dev/null
+++ b/t2/task/09_09/test_09_09.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:815b89cc3e698776c066e716b0c18bc7e9771d191d4b081df1abf90d68f06e2c
+size 18045
diff --git a/t2/task/09_10/09_10.txt b/t2/task/09_10/09_10.txt
new file mode 100644
index 0000000000000000000000000000000000000000..74908588195e72e6e0eb76b3dd47e7f152ade969
--- /dev/null
+++ b/t2/task/09_10/09_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:
+09_10
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/09_10/test_09_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/09_10
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/09_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/09_10/09_10.py
+* /xxx/ExeWorldBench/t2/task/09_10/09_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.
diff --git a/t2/task/09_10/test_09_10.png b/t2/task/09_10/test_09_10.png
new file mode 100644
index 0000000000000000000000000000000000000000..bbaa2ff46a54fb8eab4ecc8f64a3e3e4791a40c5
--- /dev/null
+++ b/t2/task/09_10/test_09_10.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:455dfc31598acbcce82c0965405f49486744b5bfbd9d2046e0ac1e67f8498345
+size 16898
diff --git a/t2/task/10_01/10_01.txt b/t2/task/10_01/10_01.txt
new file mode 100644
index 0000000000000000000000000000000000000000..6c74fd5fa3cc5086eaa475be85bdfe18b86376af
--- /dev/null
+++ b/t2/task/10_01/10_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:
+10_01
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/10_01/test_10_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/10_01
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/10_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/10_01/10_01.py
+* /xxx/ExeWorldBench/t2/task/10_01/10_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.
diff --git a/t2/task/10_01/test_10_01.png b/t2/task/10_01/test_10_01.png
new file mode 100644
index 0000000000000000000000000000000000000000..b336b2bb34778d2afe53db765f63edee987df6db
--- /dev/null
+++ b/t2/task/10_01/test_10_01.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cb87a5651683403fed72a05a3588041f1be00f9a03106815bb49ca5e11d95110
+size 21315
diff --git a/t2/task/10_02/10_02.txt b/t2/task/10_02/10_02.txt
new file mode 100644
index 0000000000000000000000000000000000000000..3414247d5f893627ec02d30c96be58c365e96ecf
--- /dev/null
+++ b/t2/task/10_02/10_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:
+10_02
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/10_02/test_10_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/10_02
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/10_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/10_02/10_02.py
+* /xxx/ExeWorldBench/t2/task/10_02/10_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.
diff --git a/t2/task/10_02/test_10_02.png b/t2/task/10_02/test_10_02.png
new file mode 100644
index 0000000000000000000000000000000000000000..0036592ad68e5c93ca405baf966de0354d0cf1d8
--- /dev/null
+++ b/t2/task/10_02/test_10_02.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f0fbf211a8ca23592c8f8532af56446b6b4b2d24d884a5189616643fe287a647
+size 17548
diff --git a/t2/task/10_03/10_03.txt b/t2/task/10_03/10_03.txt
new file mode 100644
index 0000000000000000000000000000000000000000..a5602e5bec326cf73a17011eff313515bf2e7989
--- /dev/null
+++ b/t2/task/10_03/10_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:
+10_03
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/10_03/test_10_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/10_03
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/10_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/10_03/10_03.py
+* /xxx/ExeWorldBench/t2/task/10_03/10_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.
diff --git a/t2/task/10_03/test_10_03.png b/t2/task/10_03/test_10_03.png
new file mode 100644
index 0000000000000000000000000000000000000000..353269617bdd5faa1f9a940250f45a93261b72e5
--- /dev/null
+++ b/t2/task/10_03/test_10_03.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a8759ec57d1d98f3cd582134814418b6929706e1bcd9d59838aa17c58130b06f
+size 18234
diff --git a/t2/task/10_04/10_04.txt b/t2/task/10_04/10_04.txt
new file mode 100644
index 0000000000000000000000000000000000000000..cd030427c18f0b4caf142fac5efa40c5b5e8521a
--- /dev/null
+++ b/t2/task/10_04/10_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:
+10_04
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/10_04/test_10_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/10_04
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/10_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/10_04/10_04.py
+* /xxx/ExeWorldBench/t2/task/10_04/10_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.
diff --git a/t2/task/10_04/test_10_04.png b/t2/task/10_04/test_10_04.png
new file mode 100644
index 0000000000000000000000000000000000000000..ef7af2b9fe8312b4bf9d36866bbc761a6c00a403
--- /dev/null
+++ b/t2/task/10_04/test_10_04.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:838361da3899e56862f2cde0bbf5167a5d6d5f6f23e147d26651619b84eab55c
+size 19584
diff --git a/t2/task/10_05/10_05.txt b/t2/task/10_05/10_05.txt
new file mode 100644
index 0000000000000000000000000000000000000000..8a41a9070e5efbf4cc8ea9cd8a910e47d8084657
--- /dev/null
+++ b/t2/task/10_05/10_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:
+10_05
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/10_05/test_10_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/10_05
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/10_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/10_05/10_05.py
+* /xxx/ExeWorldBench/t2/task/10_05/10_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.
diff --git a/t2/task/10_05/test_10_05.png b/t2/task/10_05/test_10_05.png
new file mode 100644
index 0000000000000000000000000000000000000000..c10a5eb904c4a52e1e8de1d82468b9af0c8f7491
--- /dev/null
+++ b/t2/task/10_05/test_10_05.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d96deb7143e9b1d703f2cba93a1f39a7ae20824188f8b468a3a5092741b827d5
+size 18665
diff --git a/t2/task/10_06/10_06.txt b/t2/task/10_06/10_06.txt
new file mode 100644
index 0000000000000000000000000000000000000000..0dd7d2dbceb09a1590dd1e36a0c6cb3464e4520a
--- /dev/null
+++ b/t2/task/10_06/10_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:
+10_06
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/10_06/test_10_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/10_06
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/10_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/10_06/10_06.py
+* /xxx/ExeWorldBench/t2/task/10_06/10_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.
diff --git a/t2/task/10_06/test_10_06.png b/t2/task/10_06/test_10_06.png
new file mode 100644
index 0000000000000000000000000000000000000000..48125d0906890877c4887f069d25dd48cfde8938
--- /dev/null
+++ b/t2/task/10_06/test_10_06.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e0ee862dccfcb63b96002163d4b3d39b5d5a573ca1b89197ed0ed651270c10f8
+size 17940
diff --git a/t2/task/10_07/10_07.txt b/t2/task/10_07/10_07.txt
new file mode 100644
index 0000000000000000000000000000000000000000..3625c278314f0371a04f18d39331137678b4c40a
--- /dev/null
+++ b/t2/task/10_07/10_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:
+10_07
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/10_07/test_10_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/10_07
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/10_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/10_07/10_07.py
+* /xxx/ExeWorldBench/t2/task/10_07/10_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.
diff --git a/t2/task/10_07/test_10_07.png b/t2/task/10_07/test_10_07.png
new file mode 100644
index 0000000000000000000000000000000000000000..37eae6c7aea623d9313bc0b3624925d94b29b5ab
--- /dev/null
+++ b/t2/task/10_07/test_10_07.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c7342e6f08a443dfd0f9deba2dd98dd6e1c823e395f93a76441defc1f9bf4e63
+size 17067
diff --git a/t2/task/10_08/10_08.txt b/t2/task/10_08/10_08.txt
new file mode 100644
index 0000000000000000000000000000000000000000..638dad5074c7746715dd4bdb06b5ac8c1aaede1e
--- /dev/null
+++ b/t2/task/10_08/10_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:
+10_08
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/10_08/test_10_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/10_08
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/10_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/10_08/10_08.py
+* /xxx/ExeWorldBench/t2/task/10_08/10_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.
diff --git a/t2/task/10_08/test_10_08.png b/t2/task/10_08/test_10_08.png
new file mode 100644
index 0000000000000000000000000000000000000000..b06f13061fc5edbb540ba2dea5924e29b909ed9f
--- /dev/null
+++ b/t2/task/10_08/test_10_08.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ab0331758657992c1d35108ac6f96e0adb23f2193f0d3f558b24f2429d985734
+size 17744
diff --git a/t2/task/10_09/10_09.txt b/t2/task/10_09/10_09.txt
new file mode 100644
index 0000000000000000000000000000000000000000..4494bf9f185813f2dd18ed59fc4de4749a78a757
--- /dev/null
+++ b/t2/task/10_09/10_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:
+10_09
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/10_09/test_10_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/10_09
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/10_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/10_09/10_09.py
+* /xxx/ExeWorldBench/t2/task/10_09/10_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.
diff --git a/t2/task/10_09/test_10_09.png b/t2/task/10_09/test_10_09.png
new file mode 100644
index 0000000000000000000000000000000000000000..a8d50c813dd7579ad2932d8ab4ff05204e1df74e
--- /dev/null
+++ b/t2/task/10_09/test_10_09.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d1ef615ccc012039a4319f54c9641b80e1e8134244431ed69efea06cf249351c
+size 18460
diff --git a/t2/task/10_10/10_10.txt b/t2/task/10_10/10_10.txt
new file mode 100644
index 0000000000000000000000000000000000000000..1e5cbb950f605d63d4844ac5a93b367d50ef67f4
--- /dev/null
+++ b/t2/task/10_10/10_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:
+10_10
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/10_10/test_10_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/10_10
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/10_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/10_10/10_10.py
+* /xxx/ExeWorldBench/t2/task/10_10/10_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.
diff --git a/t2/task/10_10/test_10_10.png b/t2/task/10_10/test_10_10.png
new file mode 100644
index 0000000000000000000000000000000000000000..cacc73a951476d0abd8203b50e98dba8fb952e4e
--- /dev/null
+++ b/t2/task/10_10/test_10_10.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2787d9d34240d157e67055673274c93bc49bfe5e4269974110ea544e759d482c
+size 17369
diff --git a/t2/task/11_01/11_01.txt b/t2/task/11_01/11_01.txt
new file mode 100644
index 0000000000000000000000000000000000000000..562fe9b192de12d5427a7f5e150400b3de7a3da2
--- /dev/null
+++ b/t2/task/11_01/11_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:
+11_01
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/11_01/test_11_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/11_01
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/11_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/11_01/11_01.py
+* /xxx/ExeWorldBench/t2/task/11_01/11_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.
diff --git a/t2/task/11_01/test_11_01.png b/t2/task/11_01/test_11_01.png
new file mode 100644
index 0000000000000000000000000000000000000000..fc98c4472ddb1d2180cb461f2b131115dad2ca5f
--- /dev/null
+++ b/t2/task/11_01/test_11_01.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2834282e71616ed4d9a563b5bd8731696dc8a1e0d4831c71b508d434668c20d1
+size 23890
diff --git a/t2/task/11_02/11_02.txt b/t2/task/11_02/11_02.txt
new file mode 100644
index 0000000000000000000000000000000000000000..42b056893f33e58d9f8ee6096d3c02b25c3d2c23
--- /dev/null
+++ b/t2/task/11_02/11_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:
+11_02
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/11_02/test_11_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/11_02
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/11_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/11_02/11_02.py
+* /xxx/ExeWorldBench/t2/task/11_02/11_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.
diff --git a/t2/task/11_02/test_11_02.png b/t2/task/11_02/test_11_02.png
new file mode 100644
index 0000000000000000000000000000000000000000..83bb6de6d73bffd5ea32b2a10930e9c0c768f274
--- /dev/null
+++ b/t2/task/11_02/test_11_02.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3ff223d4c24e3f7d0246a1862460ccb5a3ad75467afe6508df9622926d3e1381
+size 18047
diff --git a/t2/task/11_03/11_03.txt b/t2/task/11_03/11_03.txt
new file mode 100644
index 0000000000000000000000000000000000000000..0980afba3501ad6b3f49c1a0cc40c403da8ce697
--- /dev/null
+++ b/t2/task/11_03/11_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:
+11_03
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/11_03/test_11_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/11_03
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/11_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/11_03/11_03.py
+* /xxx/ExeWorldBench/t2/task/11_03/11_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.
diff --git a/t2/task/11_03/test_11_03.png b/t2/task/11_03/test_11_03.png
new file mode 100644
index 0000000000000000000000000000000000000000..56ecf2c8d0f9772f656972464b29437ae76a201c
--- /dev/null
+++ b/t2/task/11_03/test_11_03.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5b14b12824d5234d17058e905bd361880771de2a29c47df720be20cf2dd699bd
+size 18680
diff --git a/t2/task/11_04/11_04.txt b/t2/task/11_04/11_04.txt
new file mode 100644
index 0000000000000000000000000000000000000000..a2e135ff83d20232a8b377f47b3b3c2ed1ea60a5
--- /dev/null
+++ b/t2/task/11_04/11_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:
+11_04
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/11_04/test_11_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/11_04
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/11_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/11_04/11_04.py
+* /xxx/ExeWorldBench/t2/task/11_04/11_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.
diff --git a/t2/task/11_04/test_11_04.png b/t2/task/11_04/test_11_04.png
new file mode 100644
index 0000000000000000000000000000000000000000..0d7def3d3351247eb0f6998013bb412d3873ef04
--- /dev/null
+++ b/t2/task/11_04/test_11_04.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b603e3c8bf0c27d9132465039cc7aece1f37d0af5c7162bba268a4b252e7e0ce
+size 20211
diff --git a/t2/task/11_05/11_05.txt b/t2/task/11_05/11_05.txt
new file mode 100644
index 0000000000000000000000000000000000000000..c9e51e5d0956d2d61e8d0f04cf5c3beafc4dc88c
--- /dev/null
+++ b/t2/task/11_05/11_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:
+11_05
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/11_05/test_11_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/11_05
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/11_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/11_05/11_05.py
+* /xxx/ExeWorldBench/t2/task/11_05/11_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.
diff --git a/t2/task/11_05/test_11_05.png b/t2/task/11_05/test_11_05.png
new file mode 100644
index 0000000000000000000000000000000000000000..7a0bcb69aeaf4bc776435bac92533df6e92ef757
--- /dev/null
+++ b/t2/task/11_05/test_11_05.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fb5b4b36ff10250864391b3012cad4e2504257ad23bbfbfe7ebfede163e4690b
+size 19244
diff --git a/t2/task/11_06/11_06.txt b/t2/task/11_06/11_06.txt
new file mode 100644
index 0000000000000000000000000000000000000000..d3c19ef3ffab6e139890a461b8d5bab1ce0f1948
--- /dev/null
+++ b/t2/task/11_06/11_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:
+11_06
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/11_06/test_11_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/11_06
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/11_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/11_06/11_06.py
+* /xxx/ExeWorldBench/t2/task/11_06/11_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.
diff --git a/t2/task/11_06/test_11_06.png b/t2/task/11_06/test_11_06.png
new file mode 100644
index 0000000000000000000000000000000000000000..eea211d58a9c581e8fc8b977098da995dc96e315
--- /dev/null
+++ b/t2/task/11_06/test_11_06.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c59009cb144c92f4fb431d136cc2414dd164cf9e27cea26c2041d856736cf3fe
+size 18562
diff --git a/t2/task/11_07/11_07.txt b/t2/task/11_07/11_07.txt
new file mode 100644
index 0000000000000000000000000000000000000000..a24a64a70f5ce1927a7d4e357542340a48a54ed0
--- /dev/null
+++ b/t2/task/11_07/11_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:
+11_07
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/11_07/test_11_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/11_07
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/11_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/11_07/11_07.py
+* /xxx/ExeWorldBench/t2/task/11_07/11_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.
diff --git a/t2/task/11_07/test_11_07.png b/t2/task/11_07/test_11_07.png
new file mode 100644
index 0000000000000000000000000000000000000000..a4b07e0d60ee4a193634ca6e010668f5fc92383b
--- /dev/null
+++ b/t2/task/11_07/test_11_07.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f8d902c461a1832fecdba3200e7f763ccf1e78202a0daec66f9ad2a8ce0b8fc1
+size 17131
diff --git a/t2/task/11_08/11_08.txt b/t2/task/11_08/11_08.txt
new file mode 100644
index 0000000000000000000000000000000000000000..550557cabac27a9b484cdf9ee9f085a7843749d2
--- /dev/null
+++ b/t2/task/11_08/11_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:
+11_08
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/11_08/test_11_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/11_08
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/11_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/11_08/11_08.py
+* /xxx/ExeWorldBench/t2/task/11_08/11_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.
diff --git a/t2/task/11_08/test_11_08.png b/t2/task/11_08/test_11_08.png
new file mode 100644
index 0000000000000000000000000000000000000000..43030c42f239dff81e29b97ea214b2bf05d95157
--- /dev/null
+++ b/t2/task/11_08/test_11_08.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:506f7285f261cb43219d879ad111ea08d7ed7885c8eb6d63740e97bbdecba4cb
+size 18463
diff --git a/t2/task/11_09/11_09.txt b/t2/task/11_09/11_09.txt
new file mode 100644
index 0000000000000000000000000000000000000000..89febbbcdbc7c168a3d223e7e3f37039449e1973
--- /dev/null
+++ b/t2/task/11_09/11_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:
+11_09
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/11_09/test_11_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/11_09
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/11_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/11_09/11_09.py
+* /xxx/ExeWorldBench/t2/task/11_09/11_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.
diff --git a/t2/task/11_09/test_11_09.png b/t2/task/11_09/test_11_09.png
new file mode 100644
index 0000000000000000000000000000000000000000..a0273a52eee56bca386ecfd438cb8bc3cab41ad9
--- /dev/null
+++ b/t2/task/11_09/test_11_09.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:06a2dacd594d557df70bbdf6a654dd34760c893c1deec3b034c35dfb011fb2b6
+size 19005
diff --git a/t2/task/11_10/11_10.txt b/t2/task/11_10/11_10.txt
new file mode 100644
index 0000000000000000000000000000000000000000..720ff961894306109bbddfa1391592f0039d5717
--- /dev/null
+++ b/t2/task/11_10/11_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:
+11_10
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/11_10/test_11_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/11_10
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/11_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/11_10/11_10.py
+* /xxx/ExeWorldBench/t2/task/11_10/11_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.
diff --git a/t2/task/11_10/test_11_10.png b/t2/task/11_10/test_11_10.png
new file mode 100644
index 0000000000000000000000000000000000000000..915fdc6693c0cf75a0d9e2ca0d309ee59a607718
--- /dev/null
+++ b/t2/task/11_10/test_11_10.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fbba6879d4952f58e55ab6dfcf5fb1a9dd2e77cbc4774dab7eda5642064dad1f
+size 18198
diff --git a/t2/task/12_01/12_01.txt b/t2/task/12_01/12_01.txt
new file mode 100644
index 0000000000000000000000000000000000000000..c8fc211e195e6e8c8125ca7bbe2b0032e8bb3491
--- /dev/null
+++ b/t2/task/12_01/12_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:
+12_01
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/12_01/test_12_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/12_01
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/12_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/12_01/12_01.py
+* /xxx/ExeWorldBench/t2/task/12_01/12_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.
diff --git a/t2/task/12_01/test_12_01.png b/t2/task/12_01/test_12_01.png
new file mode 100644
index 0000000000000000000000000000000000000000..424083490905cc28fccc2d3e5af4c3116bc71089
--- /dev/null
+++ b/t2/task/12_01/test_12_01.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:715daebff486a65fe672be42d59e3bf766a5df046091a1cff922607e905326b6
+size 23327
diff --git a/t2/task/12_02/12_02.txt b/t2/task/12_02/12_02.txt
new file mode 100644
index 0000000000000000000000000000000000000000..738b236998e615c2e435234b89642c36a8cd9040
--- /dev/null
+++ b/t2/task/12_02/12_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:
+12_02
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/12_02/test_12_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/12_02
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/12_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/12_02/12_02.py
+* /xxx/ExeWorldBench/t2/task/12_02/12_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.
diff --git a/t2/task/12_02/test_12_02.png b/t2/task/12_02/test_12_02.png
new file mode 100644
index 0000000000000000000000000000000000000000..034d33832927bd1105fca1a8607ec7ebe4db68c8
--- /dev/null
+++ b/t2/task/12_02/test_12_02.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d1adddd0bdd7c55ac1b3395f53999abf8a5b219deba7274d170ea504ee9aa7d1
+size 18486
diff --git a/t2/task/12_03/12_03.txt b/t2/task/12_03/12_03.txt
new file mode 100644
index 0000000000000000000000000000000000000000..b0f3402f151e99944ddff64edac7a2bb32d7cf07
--- /dev/null
+++ b/t2/task/12_03/12_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:
+12_03
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/12_03/test_12_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/12_03
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/12_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/12_03/12_03.py
+* /xxx/ExeWorldBench/t2/task/12_03/12_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.
diff --git a/t2/task/12_03/test_12_03.png b/t2/task/12_03/test_12_03.png
new file mode 100644
index 0000000000000000000000000000000000000000..33a1378e65f90977e51bde89447a539647ece9c5
--- /dev/null
+++ b/t2/task/12_03/test_12_03.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:73fc3e475b2c6425b0c79dc507eb8d0dd66b1b2b191778927e765e0d867657fa
+size 19360
diff --git a/t2/task/12_04/12_04.txt b/t2/task/12_04/12_04.txt
new file mode 100644
index 0000000000000000000000000000000000000000..d71df0f5f42c1552f1e9447ee19b3728518f83c7
--- /dev/null
+++ b/t2/task/12_04/12_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:
+12_04
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/12_04/test_12_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/12_04
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/12_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/12_04/12_04.py
+* /xxx/ExeWorldBench/t2/task/12_04/12_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.
diff --git a/t2/task/12_04/test_12_04.png b/t2/task/12_04/test_12_04.png
new file mode 100644
index 0000000000000000000000000000000000000000..a126f9ad5c3a0c99bdcaf3baca5a8047e238194e
--- /dev/null
+++ b/t2/task/12_04/test_12_04.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6d7dd5e904ce5078846eb43ece37411dd58e6c61a93ffa76bdba64876050bde1
+size 20216
diff --git a/t2/task/12_05/12_05.txt b/t2/task/12_05/12_05.txt
new file mode 100644
index 0000000000000000000000000000000000000000..4d41740d55ef512743d4eb6b930c075b3e26a1d7
--- /dev/null
+++ b/t2/task/12_05/12_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:
+12_05
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/12_05/test_12_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/12_05
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/12_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/12_05/12_05.py
+* /xxx/ExeWorldBench/t2/task/12_05/12_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.
diff --git a/t2/task/12_05/test_12_05.png b/t2/task/12_05/test_12_05.png
new file mode 100644
index 0000000000000000000000000000000000000000..52e425588916ac0064ccd15239ce93d5bfd8a120
--- /dev/null
+++ b/t2/task/12_05/test_12_05.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:05f70563f6ff683afaa102b941fb01929ef0976e9c471b95d71536e90f93ef32
+size 18992
diff --git a/t2/task/12_06/12_06.txt b/t2/task/12_06/12_06.txt
new file mode 100644
index 0000000000000000000000000000000000000000..89830a46266cdd9ff8b367253239a676ec88163c
--- /dev/null
+++ b/t2/task/12_06/12_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:
+12_06
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/12_06/test_12_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/12_06
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/12_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/12_06/12_06.py
+* /xxx/ExeWorldBench/t2/task/12_06/12_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.
diff --git a/t2/task/12_06/test_12_06.png b/t2/task/12_06/test_12_06.png
new file mode 100644
index 0000000000000000000000000000000000000000..a0ac36ae1d554e1efccfb7733d25aa1f0c9c81c6
--- /dev/null
+++ b/t2/task/12_06/test_12_06.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4c68dd7754153997328a55ec6754d702c28a1d8bc87176ea334414c6b0122b77
+size 19418
diff --git a/t2/task/12_07/12_07.txt b/t2/task/12_07/12_07.txt
new file mode 100644
index 0000000000000000000000000000000000000000..dc757951657eba204cbc1bbcfde64818fc23cba3
--- /dev/null
+++ b/t2/task/12_07/12_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:
+12_07
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/12_07/test_12_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/12_07
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/12_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/12_07/12_07.py
+* /xxx/ExeWorldBench/t2/task/12_07/12_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.
diff --git a/t2/task/12_07/test_12_07.png b/t2/task/12_07/test_12_07.png
new file mode 100644
index 0000000000000000000000000000000000000000..18c4ce9f11facef1270785f1801aac1c8a8c4e52
--- /dev/null
+++ b/t2/task/12_07/test_12_07.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:972a698367f72de1ccbebebff78694ab45ca96cec9a1b2928b1be7db321e1ef5
+size 17943
diff --git a/t2/task/12_08/12_08.txt b/t2/task/12_08/12_08.txt
new file mode 100644
index 0000000000000000000000000000000000000000..9d211c62a4d59f3d3a18ac49936736a61e681366
--- /dev/null
+++ b/t2/task/12_08/12_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:
+12_08
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/12_08/test_12_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/12_08
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/12_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/12_08/12_08.py
+* /xxx/ExeWorldBench/t2/task/12_08/12_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.
diff --git a/t2/task/12_08/test_12_08.png b/t2/task/12_08/test_12_08.png
new file mode 100644
index 0000000000000000000000000000000000000000..4d01d6dcc039fe92c344ebab61ebbcc13ff0a0e8
--- /dev/null
+++ b/t2/task/12_08/test_12_08.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:51dcf32576b2c759e35aefd5d2d3328d05742c9fb5df67c42f45e72eb235e6ff
+size 19179
diff --git a/t2/task/12_09/12_09.txt b/t2/task/12_09/12_09.txt
new file mode 100644
index 0000000000000000000000000000000000000000..abfba962b227a2b02b3ed57fa11444d3fef4054f
--- /dev/null
+++ b/t2/task/12_09/12_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:
+12_09
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/12_09/test_12_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/12_09
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/12_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/12_09/12_09.py
+* /xxx/ExeWorldBench/t2/task/12_09/12_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.
diff --git a/t2/task/12_09/test_12_09.png b/t2/task/12_09/test_12_09.png
new file mode 100644
index 0000000000000000000000000000000000000000..dc2bb334d0ac3854c71c5bdf8ab32d72eca89dfd
--- /dev/null
+++ b/t2/task/12_09/test_12_09.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d3c950b4df1f9b805df8e0c85fc880ca997ea057798bf907e97fa88c3d3d2e5f
+size 19568
diff --git a/t2/task/12_10/12_10.txt b/t2/task/12_10/12_10.txt
new file mode 100644
index 0000000000000000000000000000000000000000..8051f0619bd5ebc15577d0297228fc5191bc869c
--- /dev/null
+++ b/t2/task/12_10/12_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:
+12_10
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/12_10/test_12_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/12_10
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/12_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/12_10/12_10.py
+* /xxx/ExeWorldBench/t2/task/12_10/12_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.
diff --git a/t2/task/12_10/test_12_10.png b/t2/task/12_10/test_12_10.png
new file mode 100644
index 0000000000000000000000000000000000000000..54aa95908bd5cee1e3fc2cbac97ed898b635b1f5
--- /dev/null
+++ b/t2/task/12_10/test_12_10.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c9ff40b3ff923a14ecb14fc67b915f1c910aafd690aa94e632bdb0d188ab399c
+size 18870
diff --git a/t2/task/13_01/13_01.txt b/t2/task/13_01/13_01.txt
new file mode 100644
index 0000000000000000000000000000000000000000..d057bcc28ae87a98496ab4fd5423095b0c7f5b77
--- /dev/null
+++ b/t2/task/13_01/13_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:
+13_01
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/13_01/test_13_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/13_01
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/13_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/13_01/13_01.py
+* /xxx/ExeWorldBench/t2/task/13_01/13_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.
diff --git a/t2/task/13_01/test_13_01.png b/t2/task/13_01/test_13_01.png
new file mode 100644
index 0000000000000000000000000000000000000000..011d79557a2377807b19818a01d16d0376fea2fa
--- /dev/null
+++ b/t2/task/13_01/test_13_01.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9b8680a9a4eedfdf15d3796cdc1302e8355bdeed3546caecfd6c7d0ddb3ecdda
+size 24971
diff --git a/t2/task/13_02/13_02.txt b/t2/task/13_02/13_02.txt
new file mode 100644
index 0000000000000000000000000000000000000000..6aa5798d3a0e19e5b5600257702357d3d5c76575
--- /dev/null
+++ b/t2/task/13_02/13_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:
+13_02
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/13_02/test_13_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/13_02
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/13_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/13_02/13_02.py
+* /xxx/ExeWorldBench/t2/task/13_02/13_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.
diff --git a/t2/task/13_02/test_13_02.png b/t2/task/13_02/test_13_02.png
new file mode 100644
index 0000000000000000000000000000000000000000..40d3d455a3f6e1d6cfd41b9a77c15481f2ea12bf
--- /dev/null
+++ b/t2/task/13_02/test_13_02.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f3db7949212c49ff3d0ff2555405071e662d9c003726eb42d0432a01a8e2a111
+size 22073
diff --git a/t2/task/13_03/13_03.txt b/t2/task/13_03/13_03.txt
new file mode 100644
index 0000000000000000000000000000000000000000..9878fab33baad569c6c67bacee1b103029a6a7e4
--- /dev/null
+++ b/t2/task/13_03/13_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:
+13_03
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/13_03/test_13_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/13_03
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/13_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/13_03/13_03.py
+* /xxx/ExeWorldBench/t2/task/13_03/13_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.
diff --git a/t2/task/13_03/test_13_03.png b/t2/task/13_03/test_13_03.png
new file mode 100644
index 0000000000000000000000000000000000000000..119cf9c4a5e88a53e76da0ea6ad320b5e4c34536
--- /dev/null
+++ b/t2/task/13_03/test_13_03.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7efa450a30ac611be4cb0bd50cfcfd2c8bad24510898109b6e07393d34db53dd
+size 23138
diff --git a/t2/task/13_04/13_04.txt b/t2/task/13_04/13_04.txt
new file mode 100644
index 0000000000000000000000000000000000000000..a6372da87091990516f77dbd8d0c02e0a2bb5017
--- /dev/null
+++ b/t2/task/13_04/13_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:
+13_04
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/13_04/test_13_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/13_04
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/13_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/13_04/13_04.py
+* /xxx/ExeWorldBench/t2/task/13_04/13_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.
diff --git a/t2/task/13_04/test_13_04.png b/t2/task/13_04/test_13_04.png
new file mode 100644
index 0000000000000000000000000000000000000000..a7a55931485a2a73c267f2578fd4e722dcc87e20
--- /dev/null
+++ b/t2/task/13_04/test_13_04.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:804e40b4d3ce66728c11f35cc26a7e08386147e470d9421acf86c922fcd87619
+size 23211
diff --git a/t2/task/13_05/13_05.txt b/t2/task/13_05/13_05.txt
new file mode 100644
index 0000000000000000000000000000000000000000..f1e630297d7635ea79251dbd3cc87ca5a2b7861a
--- /dev/null
+++ b/t2/task/13_05/13_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:
+13_05
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/13_05/test_13_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/13_05
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/13_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/13_05/13_05.py
+* /xxx/ExeWorldBench/t2/task/13_05/13_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.
diff --git a/t2/task/13_05/test_13_05.png b/t2/task/13_05/test_13_05.png
new file mode 100644
index 0000000000000000000000000000000000000000..ed03f562441f57d8a2103cb7f72e7de2e6f92968
--- /dev/null
+++ b/t2/task/13_05/test_13_05.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3c00832414496309d20fddbad808ef4b0dbfd2491fce26a713790d51b0fd513f
+size 22256
diff --git a/t2/task/13_06/13_06.txt b/t2/task/13_06/13_06.txt
new file mode 100644
index 0000000000000000000000000000000000000000..c73cdeecf2b264a31ff846846c139f6fb6f4bda1
--- /dev/null
+++ b/t2/task/13_06/13_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:
+13_06
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/13_06/test_13_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/13_06
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/13_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/13_06/13_06.py
+* /xxx/ExeWorldBench/t2/task/13_06/13_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.
diff --git a/t2/task/13_06/test_13_06.png b/t2/task/13_06/test_13_06.png
new file mode 100644
index 0000000000000000000000000000000000000000..52158db551d205fb29782cfb4216e369e8d1dfce
--- /dev/null
+++ b/t2/task/13_06/test_13_06.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:91008d83175b7f494dee38afb9f30afa1e95d6a3e230096aba7cb8c674e8a481
+size 23155
diff --git a/t2/task/13_07/13_07.txt b/t2/task/13_07/13_07.txt
new file mode 100644
index 0000000000000000000000000000000000000000..e83a1bdd9c9186267171d7d262ae436d4237f8ee
--- /dev/null
+++ b/t2/task/13_07/13_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:
+13_07
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/13_07/test_13_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/13_07
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/13_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/13_07/13_07.py
+* /xxx/ExeWorldBench/t2/task/13_07/13_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.
diff --git a/t2/task/13_07/test_13_07.png b/t2/task/13_07/test_13_07.png
new file mode 100644
index 0000000000000000000000000000000000000000..35a69af472ddabb38b18018d14df7e9d3963357d
--- /dev/null
+++ b/t2/task/13_07/test_13_07.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:16c91e397145014b9caaa85fbb8283c05fe665fc9157c402b6785eefe1830602
+size 22223
diff --git a/t2/task/13_08/13_08.txt b/t2/task/13_08/13_08.txt
new file mode 100644
index 0000000000000000000000000000000000000000..1a710abe740eec98a8f7b0228442fbc485e7b467
--- /dev/null
+++ b/t2/task/13_08/13_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:
+13_08
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/13_08/test_13_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/13_08
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/13_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/13_08/13_08.py
+* /xxx/ExeWorldBench/t2/task/13_08/13_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.
diff --git a/t2/task/13_08/test_13_08.png b/t2/task/13_08/test_13_08.png
new file mode 100644
index 0000000000000000000000000000000000000000..0971453dca3ae8921b6c63c2868369970ade2bb9
--- /dev/null
+++ b/t2/task/13_08/test_13_08.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ecc9f14fad9b225d63a008f51c0824d7a384f323a65a9899aaa84dfc8cddb498
+size 22319
diff --git a/t2/task/13_09/13_09.txt b/t2/task/13_09/13_09.txt
new file mode 100644
index 0000000000000000000000000000000000000000..cf7fc2e76aaa32c7236d0f8709fef4a65ef948c6
--- /dev/null
+++ b/t2/task/13_09/13_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:
+13_09
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/13_09/test_13_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/13_09
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/13_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/13_09/13_09.py
+* /xxx/ExeWorldBench/t2/task/13_09/13_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.
diff --git a/t2/task/13_09/test_13_09.png b/t2/task/13_09/test_13_09.png
new file mode 100644
index 0000000000000000000000000000000000000000..191568494b32a321a525c3185f1717cd973bf16a
--- /dev/null
+++ b/t2/task/13_09/test_13_09.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:30ac7363d20be887a5c016148111e0c47a47cbe81e07e6d5227648518ba7b642
+size 22730
diff --git a/t2/task/13_10/13_10.txt b/t2/task/13_10/13_10.txt
new file mode 100644
index 0000000000000000000000000000000000000000..96f354534813c767622bdf80851eee0c9aa9bac0
--- /dev/null
+++ b/t2/task/13_10/13_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:
+13_10
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/13_10/test_13_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/13_10
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/13_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/13_10/13_10.py
+* /xxx/ExeWorldBench/t2/task/13_10/13_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.
diff --git a/t2/task/13_10/test_13_10.png b/t2/task/13_10/test_13_10.png
new file mode 100644
index 0000000000000000000000000000000000000000..53d484a4f976eccc95ca4eef76dce65cc973ec79
--- /dev/null
+++ b/t2/task/13_10/test_13_10.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7156426839044f358577cd24d43d9424bf4bc51b6ff4f811121b3225e34aadce
+size 21800
diff --git a/t2/task_image/04_01/04_01.txt b/t2/task_image/04_01/04_01.txt
new file mode 100644
index 0000000000000000000000000000000000000000..49e328e4193f9b85d5b41b8b19ef2294997a2945
--- /dev/null
+++ b/t2/task_image/04_01/04_01.txt
@@ -0,0 +1,89 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image and motion reference frames, 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:
+04_01
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task_image/04_01/test_04_01.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t2/task_image/04_01/frame/04_01_000.png, /xxx/ExeWorldBench/t2/task_image/04_01/frame/04_01_001.png, /xxx/ExeWorldBench/t2/task_image/04_01/frame/04_01_002.png, /xxx/ExeWorldBench/t2/task_image/04_01/frame/04_01_003.png, /xxx/ExeWorldBench/t2/task_image/04_01/frame/04_01_004.png, /xxx/ExeWorldBench/t2/task_image/04_01/frame/04_01_005.png, /xxx/ExeWorldBench/t2/task_image/04_01/frame/04_01_006.png, /xxx/ExeWorldBench/t2/task_image/04_01/frame/04_01_007.png
+
+Use only the reference image and motion reference frames 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_image/04_01
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task_image/04_01. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given:
+
+1. A visual reference image of a multi-stage mechanical chain.
+2. A sequence of ordered motion reference frames illustrating how the mechanical chain is approximately intended to operate.
+
+Both the reference image and the motion frames provide approximate visual guidance rather than an exact executable specification.
+
+The reference image mainly indicates the mechanical components involved and their approximate spatial arrangement, while the motion frames provide additional cues about the approximate motion, interaction, and progression of the mechanical chain.
+
+The exact positions, distances, orientations, trajectories, timing, and geometric relationships shown in these visual references may not directly form a physically executable system.
+
+Your task is to reason about how the components should mechanically interact, infer the intended chain behavior from the visual references, adjust the spatial configuration and motion details 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 visual references, but to construct a physically executable mechanical system in which the initial action propagates through all stages and produces the intended chain reaction through realistic physical interactions.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure indicated by the visual references.
+- Use the ordered motion frames as approximate cues to infer the intended motion direction, stage order, component interactions, and causal progression of the chain.
+- The visual references should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, trajectories, or other geometric and motion 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.
+- The provided motion frames are approximate behavioral references, not target poses or trajectories to be directly reproduced.
+- Do not directly prescribe the per-frame position or rotation of components to imitate the provided motion frames.
+- 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, isolated poses, 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 generated motion should follow the overall behavioral progression indicated by the visual references while remaining physically executable.
+- The animation must be long enough to show the complete mechanical chain.
+- An implementation that only visually matches several reference frames but fails to produce a continuous physical chain between them is considered incomplete.
+- 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 references 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_image/04_01/04_01.py
+* /xxx/ExeWorldBench/t2/task_image/04_01/04_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.
diff --git a/t2/task_image/04_01/frame/04_01_000.png b/t2/task_image/04_01/frame/04_01_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..00270398f767cc75216271bbd24e049c5c7e0929
--- /dev/null
+++ b/t2/task_image/04_01/frame/04_01_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:25f9503699887d4eadb241f165710d1bfb5b49d402b1850b37971eaca6f25c71
+size 142553
diff --git a/t2/task_image/04_01/frame/04_01_001.png b/t2/task_image/04_01/frame/04_01_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..d06d0b77640e14964d11e6b8e5a155d42a6f7662
--- /dev/null
+++ b/t2/task_image/04_01/frame/04_01_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cab6b69a47199cebc0e46dee19388ee5bfb62a4325d746aaa47acdf8aaddf164
+size 140416
diff --git a/t2/task_image/04_01/frame/04_01_002.png b/t2/task_image/04_01/frame/04_01_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..b90333e19b809eb9a033d60e4d741bba5142ca10
--- /dev/null
+++ b/t2/task_image/04_01/frame/04_01_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b44a1b84aad20f45978f42f34371db8eda57b2147c5cbcba25e4db125475fce7
+size 147518
diff --git a/t2/task_image/04_01/frame/04_01_003.png b/t2/task_image/04_01/frame/04_01_003.png
new file mode 100644
index 0000000000000000000000000000000000000000..1f0d209a222d7b505fd1ad72110390e29eb0006f
--- /dev/null
+++ b/t2/task_image/04_01/frame/04_01_003.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4462ee32c2481fc49323c2d03483ee786528f0079ba890059ac1da8c2d12ba6c
+size 153847
diff --git a/t2/task_image/04_01/frame/04_01_004.png b/t2/task_image/04_01/frame/04_01_004.png
new file mode 100644
index 0000000000000000000000000000000000000000..6640ecea9056a11e6bb031a1f32a098181841cda
--- /dev/null
+++ b/t2/task_image/04_01/frame/04_01_004.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0d46dfaff73f9ccfc238ae1a8d68c1d91acdb51adfbacedb1c389864096f8682
+size 153937
diff --git a/t2/task_image/04_01/frame/04_01_005.png b/t2/task_image/04_01/frame/04_01_005.png
new file mode 100644
index 0000000000000000000000000000000000000000..a29f297e610a69a50e17e99a1370642611a17dd6
--- /dev/null
+++ b/t2/task_image/04_01/frame/04_01_005.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d08477b0c7c227fec3c809ac0b82b9e77b3a0bcabe6c322d62fe6b37f5f020d8
+size 154597
diff --git a/t2/task_image/04_01/frame/04_01_006.png b/t2/task_image/04_01/frame/04_01_006.png
new file mode 100644
index 0000000000000000000000000000000000000000..c8452d1b014551a7a9ff66fa71e5e335b5e197d0
--- /dev/null
+++ b/t2/task_image/04_01/frame/04_01_006.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:374e65133179eac8ed193b52c340426347464f2a6acda954d32fc201cd2ca780
+size 154679
diff --git a/t2/task_image/04_01/frame/04_01_007.png b/t2/task_image/04_01/frame/04_01_007.png
new file mode 100644
index 0000000000000000000000000000000000000000..16ecce42f387d7d819e2eded941ec4564eb48678
--- /dev/null
+++ b/t2/task_image/04_01/frame/04_01_007.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:85afc601e9a6c48631d22a840fe1584edf7efd2a6c0cb8ff02e32dd52866634c
+size 153951
diff --git a/t2/task_image/04_01/test_04_01.png b/t2/task_image/04_01/test_04_01.png
new file mode 100644
index 0000000000000000000000000000000000000000..0b6628fe2b6d38f0ec21c23d09b6e0ef16e96492
--- /dev/null
+++ b/t2/task_image/04_01/test_04_01.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:658a73a97aa258414dd8e6ff47aa72d28bfe1effbe1de1a8955cc839f5c2259e
+size 15113
diff --git a/t2/task_image/04_02/04_02.txt b/t2/task_image/04_02/04_02.txt
new file mode 100644
index 0000000000000000000000000000000000000000..e353ed5e79df9d9e65d87c01ad6c0d4e1a5ffba2
--- /dev/null
+++ b/t2/task_image/04_02/04_02.txt
@@ -0,0 +1,89 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image and motion reference frames, 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:
+04_02
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task_image/04_02/test_04_02.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t2/task_image/04_02/frame/04_02_000.png, /xxx/ExeWorldBench/t2/task_image/04_02/frame/04_02_001.png, /xxx/ExeWorldBench/t2/task_image/04_02/frame/04_02_002.png, /xxx/ExeWorldBench/t2/task_image/04_02/frame/04_02_003.png, /xxx/ExeWorldBench/t2/task_image/04_02/frame/04_02_004.png
+
+Use only the reference image and motion reference frames 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_image/04_02
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task_image/04_02. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given:
+
+1. A visual reference image of a multi-stage mechanical chain.
+2. A sequence of ordered motion reference frames illustrating how the mechanical chain is approximately intended to operate.
+
+Both the reference image and the motion frames provide approximate visual guidance rather than an exact executable specification.
+
+The reference image mainly indicates the mechanical components involved and their approximate spatial arrangement, while the motion frames provide additional cues about the approximate motion, interaction, and progression of the mechanical chain.
+
+The exact positions, distances, orientations, trajectories, timing, and geometric relationships shown in these visual references may not directly form a physically executable system.
+
+Your task is to reason about how the components should mechanically interact, infer the intended chain behavior from the visual references, adjust the spatial configuration and motion details 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 visual references, but to construct a physically executable mechanical system in which the initial action propagates through all stages and produces the intended chain reaction through realistic physical interactions.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure indicated by the visual references.
+- Use the ordered motion frames as approximate cues to infer the intended motion direction, stage order, component interactions, and causal progression of the chain.
+- The visual references should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, trajectories, or other geometric and motion 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.
+- The provided motion frames are approximate behavioral references, not target poses or trajectories to be directly reproduced.
+- Do not directly prescribe the per-frame position or rotation of components to imitate the provided motion frames.
+- 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, isolated poses, 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 generated motion should follow the overall behavioral progression indicated by the visual references while remaining physically executable.
+- The animation must be long enough to show the complete mechanical chain.
+- An implementation that only visually matches several reference frames but fails to produce a continuous physical chain between them is considered incomplete.
+- 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 references 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_image/04_02/04_02.py
+* /xxx/ExeWorldBench/t2/task_image/04_02/04_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.
diff --git a/t2/task_image/04_02/frame/04_02_000.png b/t2/task_image/04_02/frame/04_02_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..6c942e332cd37e6144787c91177c7727943997f6
--- /dev/null
+++ b/t2/task_image/04_02/frame/04_02_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f53835abd0d0904b9001787a7c3d8dc56e67c00609e1be0367403732f958e5c9
+size 137942
diff --git a/t2/task_image/04_02/frame/04_02_001.png b/t2/task_image/04_02/frame/04_02_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..059af5c2442b0be8f15fdce459470d74354ae217
--- /dev/null
+++ b/t2/task_image/04_02/frame/04_02_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ae5c472f3a17c823de8327e4255428c35ac356dc8a1a4eb91fb8cfd87853da75
+size 144994
diff --git a/t2/task_image/04_02/frame/04_02_002.png b/t2/task_image/04_02/frame/04_02_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..ac908e319693f75eb5e8bddbc5a566270930805b
--- /dev/null
+++ b/t2/task_image/04_02/frame/04_02_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:41cafd8f30b12408e581b8a21aa580c87dc7a199770c38db1f40a17970bbeef9
+size 149349
diff --git a/t2/task_image/04_02/frame/04_02_003.png b/t2/task_image/04_02/frame/04_02_003.png
new file mode 100644
index 0000000000000000000000000000000000000000..23a466a05e8297059f52063949b4837185ca00cb
--- /dev/null
+++ b/t2/task_image/04_02/frame/04_02_003.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:815ec8261964ffb84ef38368f5797f2b7e597d6b5322aea729c214cbaa749953
+size 152627
diff --git a/t2/task_image/04_02/frame/04_02_004.png b/t2/task_image/04_02/frame/04_02_004.png
new file mode 100644
index 0000000000000000000000000000000000000000..4c049bb904aeb50d875ed29753270e3929a8eb41
--- /dev/null
+++ b/t2/task_image/04_02/frame/04_02_004.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8c2f0e0693ae2fedc8dcb5fbd8b2173767c0c5e7b5eac34a0d02892412d52d04
+size 152223
diff --git a/t2/task_image/04_02/test_04_02.png b/t2/task_image/04_02/test_04_02.png
new file mode 100644
index 0000000000000000000000000000000000000000..cd3eee9b1a18ad227a44891c935b3985277ff7f9
--- /dev/null
+++ b/t2/task_image/04_02/test_04_02.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e5e18d18ce7beb67adf612bd35e1b279cc6645970363564811c12a74b7dbbd3e
+size 13728
diff --git a/t2/task_image/04_03/04_03.txt b/t2/task_image/04_03/04_03.txt
new file mode 100644
index 0000000000000000000000000000000000000000..69d7583e1fd349bae2e37fe4668517dd110f8f6f
--- /dev/null
+++ b/t2/task_image/04_03/04_03.txt
@@ -0,0 +1,89 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image and motion reference frames, 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:
+04_03
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task_image/04_03/test_04_03.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t2/task_image/04_03/frame/04_03_000.png, /xxx/ExeWorldBench/t2/task_image/04_03/frame/04_03_001.png, /xxx/ExeWorldBench/t2/task_image/04_03/frame/04_03_002.png, /xxx/ExeWorldBench/t2/task_image/04_03/frame/04_03_003.png, /xxx/ExeWorldBench/t2/task_image/04_03/frame/04_03_004.png
+
+Use only the reference image and motion reference frames 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_image/04_03
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task_image/04_03. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given:
+
+1. A visual reference image of a multi-stage mechanical chain.
+2. A sequence of ordered motion reference frames illustrating how the mechanical chain is approximately intended to operate.
+
+Both the reference image and the motion frames provide approximate visual guidance rather than an exact executable specification.
+
+The reference image mainly indicates the mechanical components involved and their approximate spatial arrangement, while the motion frames provide additional cues about the approximate motion, interaction, and progression of the mechanical chain.
+
+The exact positions, distances, orientations, trajectories, timing, and geometric relationships shown in these visual references may not directly form a physically executable system.
+
+Your task is to reason about how the components should mechanically interact, infer the intended chain behavior from the visual references, adjust the spatial configuration and motion details 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 visual references, but to construct a physically executable mechanical system in which the initial action propagates through all stages and produces the intended chain reaction through realistic physical interactions.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure indicated by the visual references.
+- Use the ordered motion frames as approximate cues to infer the intended motion direction, stage order, component interactions, and causal progression of the chain.
+- The visual references should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, trajectories, or other geometric and motion 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.
+- The provided motion frames are approximate behavioral references, not target poses or trajectories to be directly reproduced.
+- Do not directly prescribe the per-frame position or rotation of components to imitate the provided motion frames.
+- 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, isolated poses, 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 generated motion should follow the overall behavioral progression indicated by the visual references while remaining physically executable.
+- The animation must be long enough to show the complete mechanical chain.
+- An implementation that only visually matches several reference frames but fails to produce a continuous physical chain between them is considered incomplete.
+- 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 references 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_image/04_03/04_03.py
+* /xxx/ExeWorldBench/t2/task_image/04_03/04_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.
diff --git a/t2/task_image/04_03/frame/04_03_000.png b/t2/task_image/04_03/frame/04_03_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..855774f241a843e4bdfab258cae4f2d4674f40d8
--- /dev/null
+++ b/t2/task_image/04_03/frame/04_03_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6c1f5849dd8db62a4dd961c6094fdb60c98db3a12e9f4c4f0749daf0fe3e01a5
+size 155484
diff --git a/t2/task_image/04_03/frame/04_03_001.png b/t2/task_image/04_03/frame/04_03_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..49ab2f6fc4176013858617376160ef4f89e8b8d4
--- /dev/null
+++ b/t2/task_image/04_03/frame/04_03_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:10c2c5801d22fdefed7236c9ccd0bd6df1ed67c3b1bb3216df2215c108ede768
+size 158147
diff --git a/t2/task_image/04_03/frame/04_03_002.png b/t2/task_image/04_03/frame/04_03_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..16c5974877084258826c1f3699c034b255ab30d0
--- /dev/null
+++ b/t2/task_image/04_03/frame/04_03_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fc1b1c0f6ce264705072777cf2dbccabe3795bd88c1a9cb4b976cb878b368a31
+size 160091
diff --git a/t2/task_image/04_03/frame/04_03_003.png b/t2/task_image/04_03/frame/04_03_003.png
new file mode 100644
index 0000000000000000000000000000000000000000..03239c67971de60dd57ca1e3d7c742e66a5060cd
--- /dev/null
+++ b/t2/task_image/04_03/frame/04_03_003.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dec0e6edd77f6a9bbce39a89ee75a928805b7f5fd4af51a4cf7dde0e2042e208
+size 161913
diff --git a/t2/task_image/04_03/frame/04_03_004.png b/t2/task_image/04_03/frame/04_03_004.png
new file mode 100644
index 0000000000000000000000000000000000000000..5157f909876242def7cc4c0566b837797c8e2285
--- /dev/null
+++ b/t2/task_image/04_03/frame/04_03_004.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:775a1de7d19e75a6935a16bff0e60dab4f5ea3e9b43b3398df438d5c9331f1a7
+size 161656
diff --git a/t2/task_image/04_03/test_04_03.png b/t2/task_image/04_03/test_04_03.png
new file mode 100644
index 0000000000000000000000000000000000000000..c4fbfd85ef33635fd7187cfd5cb7890769b608d5
--- /dev/null
+++ b/t2/task_image/04_03/test_04_03.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b8362cd7d9acb8d83f94b66bff8d980bb23ad9d6bed05f9e13d1e1ba20f4a4e2
+size 15403
diff --git a/t2/task_image/04_04/04_04.txt b/t2/task_image/04_04/04_04.txt
new file mode 100644
index 0000000000000000000000000000000000000000..006e5a666687238d7589cbe2838b2fbcc581a027
--- /dev/null
+++ b/t2/task_image/04_04/04_04.txt
@@ -0,0 +1,89 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image and motion reference frames, 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:
+04_04
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task_image/04_04/test_04_04.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t2/task_image/04_04/frame/04_04_000.png, /xxx/ExeWorldBench/t2/task_image/04_04/frame/04_04_001.png, /xxx/ExeWorldBench/t2/task_image/04_04/frame/04_04_002.png, /xxx/ExeWorldBench/t2/task_image/04_04/frame/04_04_003.png, /xxx/ExeWorldBench/t2/task_image/04_04/frame/04_04_004.png
+
+Use only the reference image and motion reference frames 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_image/04_04
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task_image/04_04. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given:
+
+1. A visual reference image of a multi-stage mechanical chain.
+2. A sequence of ordered motion reference frames illustrating how the mechanical chain is approximately intended to operate.
+
+Both the reference image and the motion frames provide approximate visual guidance rather than an exact executable specification.
+
+The reference image mainly indicates the mechanical components involved and their approximate spatial arrangement, while the motion frames provide additional cues about the approximate motion, interaction, and progression of the mechanical chain.
+
+The exact positions, distances, orientations, trajectories, timing, and geometric relationships shown in these visual references may not directly form a physically executable system.
+
+Your task is to reason about how the components should mechanically interact, infer the intended chain behavior from the visual references, adjust the spatial configuration and motion details 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 visual references, but to construct a physically executable mechanical system in which the initial action propagates through all stages and produces the intended chain reaction through realistic physical interactions.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure indicated by the visual references.
+- Use the ordered motion frames as approximate cues to infer the intended motion direction, stage order, component interactions, and causal progression of the chain.
+- The visual references should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, trajectories, or other geometric and motion 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.
+- The provided motion frames are approximate behavioral references, not target poses or trajectories to be directly reproduced.
+- Do not directly prescribe the per-frame position or rotation of components to imitate the provided motion frames.
+- 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, isolated poses, 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 generated motion should follow the overall behavioral progression indicated by the visual references while remaining physically executable.
+- The animation must be long enough to show the complete mechanical chain.
+- An implementation that only visually matches several reference frames but fails to produce a continuous physical chain between them is considered incomplete.
+- 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 references 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_image/04_04/04_04.py
+* /xxx/ExeWorldBench/t2/task_image/04_04/04_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.
diff --git a/t2/task_image/04_04/frame/04_04_000.png b/t2/task_image/04_04/frame/04_04_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..9894eb4e13c6938fa4329698a1f4dac29878ebdc
--- /dev/null
+++ b/t2/task_image/04_04/frame/04_04_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:850a9b80a2dc3febef43e59a2242e554941a756f35edeebc30c40accb2362747
+size 147004
diff --git a/t2/task_image/04_04/frame/04_04_001.png b/t2/task_image/04_04/frame/04_04_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..1913980335b9cee98954e4280099035f7ccdbd1c
--- /dev/null
+++ b/t2/task_image/04_04/frame/04_04_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:857ecd9bb6e71efab168c31dfa894a026c51d821d4afab4d95773d53ccda61de
+size 150015
diff --git a/t2/task_image/04_04/frame/04_04_002.png b/t2/task_image/04_04/frame/04_04_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..344abf4fad1be4aececaa74113597f99c9e7019a
--- /dev/null
+++ b/t2/task_image/04_04/frame/04_04_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:04f36673ddfb12287434f2717a758c43e26d603346b7ef136e6293f38b809962
+size 150982
diff --git a/t2/task_image/04_04/frame/04_04_003.png b/t2/task_image/04_04/frame/04_04_003.png
new file mode 100644
index 0000000000000000000000000000000000000000..af56ca8d9fd49328cd0db6017514380b2ff05ae0
--- /dev/null
+++ b/t2/task_image/04_04/frame/04_04_003.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:953a4bcb93c3a4348585505e43b7dca4611c0f6f3b0f4dc8c6de6629543f6dfb
+size 152176
diff --git a/t2/task_image/04_04/frame/04_04_004.png b/t2/task_image/04_04/frame/04_04_004.png
new file mode 100644
index 0000000000000000000000000000000000000000..62e3296c7fd772d40630b388f2af55dac65135f0
--- /dev/null
+++ b/t2/task_image/04_04/frame/04_04_004.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:157195b617821daf91dce41aee0ecec8dc30c021bfe923db0a975aa3ce0d7769
+size 152256
diff --git a/t2/task_image/04_04/test_04_04.png b/t2/task_image/04_04/test_04_04.png
new file mode 100644
index 0000000000000000000000000000000000000000..05679456e83ce1f7177d3b5b447859297638c91f
--- /dev/null
+++ b/t2/task_image/04_04/test_04_04.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7e53eda59587ebdc39a167d0a6e018a9ebead12206f4e723fcb67a58d30dc6d6
+size 16033
diff --git a/t2/task_image/04_05/04_05.txt b/t2/task_image/04_05/04_05.txt
new file mode 100644
index 0000000000000000000000000000000000000000..949405765ceec6ce3b03bbf0bf0b63749b820482
--- /dev/null
+++ b/t2/task_image/04_05/04_05.txt
@@ -0,0 +1,89 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image and motion reference frames, 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:
+04_05
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task_image/04_05/test_04_05.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t2/task_image/04_05/frame/04_05_000.png, /xxx/ExeWorldBench/t2/task_image/04_05/frame/04_05_001.png, /xxx/ExeWorldBench/t2/task_image/04_05/frame/04_05_002.png, /xxx/ExeWorldBench/t2/task_image/04_05/frame/04_05_003.png, /xxx/ExeWorldBench/t2/task_image/04_05/frame/04_05_004.png
+
+Use only the reference image and motion reference frames 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_image/04_05
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task_image/04_05. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given:
+
+1. A visual reference image of a multi-stage mechanical chain.
+2. A sequence of ordered motion reference frames illustrating how the mechanical chain is approximately intended to operate.
+
+Both the reference image and the motion frames provide approximate visual guidance rather than an exact executable specification.
+
+The reference image mainly indicates the mechanical components involved and their approximate spatial arrangement, while the motion frames provide additional cues about the approximate motion, interaction, and progression of the mechanical chain.
+
+The exact positions, distances, orientations, trajectories, timing, and geometric relationships shown in these visual references may not directly form a physically executable system.
+
+Your task is to reason about how the components should mechanically interact, infer the intended chain behavior from the visual references, adjust the spatial configuration and motion details 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 visual references, but to construct a physically executable mechanical system in which the initial action propagates through all stages and produces the intended chain reaction through realistic physical interactions.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure indicated by the visual references.
+- Use the ordered motion frames as approximate cues to infer the intended motion direction, stage order, component interactions, and causal progression of the chain.
+- The visual references should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, trajectories, or other geometric and motion 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.
+- The provided motion frames are approximate behavioral references, not target poses or trajectories to be directly reproduced.
+- Do not directly prescribe the per-frame position or rotation of components to imitate the provided motion frames.
+- 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, isolated poses, 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 generated motion should follow the overall behavioral progression indicated by the visual references while remaining physically executable.
+- The animation must be long enough to show the complete mechanical chain.
+- An implementation that only visually matches several reference frames but fails to produce a continuous physical chain between them is considered incomplete.
+- 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 references 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_image/04_05/04_05.py
+* /xxx/ExeWorldBench/t2/task_image/04_05/04_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.
diff --git a/t2/task_image/04_05/frame/04_05_000.png b/t2/task_image/04_05/frame/04_05_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..1251ef22a96e19bc1aecc1731de74067bc1e7b59
--- /dev/null
+++ b/t2/task_image/04_05/frame/04_05_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fe6bc7beb91986bb03197c0714c39e741a8dc7c6ae1d5c00af974dc09cba4e95
+size 157684
diff --git a/t2/task_image/04_05/frame/04_05_001.png b/t2/task_image/04_05/frame/04_05_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..778c06c704681d93a7fe615a9b1a277c5002c38f
--- /dev/null
+++ b/t2/task_image/04_05/frame/04_05_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:66d4fc94cf4907ce55320fcc7fc96d79ff528692d74c9ae88bb2bcadacf42499
+size 159036
diff --git a/t2/task_image/04_05/frame/04_05_002.png b/t2/task_image/04_05/frame/04_05_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..aa3829128492f24073be63e71ea5b56b3d7d4afd
--- /dev/null
+++ b/t2/task_image/04_05/frame/04_05_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:14be5f30bedd6ae86008d8b891808a36d5c4831b7a9f8ebaee023d635c806e67
+size 159387
diff --git a/t2/task_image/04_05/frame/04_05_003.png b/t2/task_image/04_05/frame/04_05_003.png
new file mode 100644
index 0000000000000000000000000000000000000000..9640dabb66296603a7ecf6eac1febc62317c4fce
--- /dev/null
+++ b/t2/task_image/04_05/frame/04_05_003.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:716a84dbf59d7485ccc616737f7a047c4edc3a2b0c6cc50ce1b8f3b71aa30165
+size 163880
diff --git a/t2/task_image/04_05/frame/04_05_004.png b/t2/task_image/04_05/frame/04_05_004.png
new file mode 100644
index 0000000000000000000000000000000000000000..2c786768036da149526f8dd7c230e2bd38fcd603
--- /dev/null
+++ b/t2/task_image/04_05/frame/04_05_004.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fd1c7912f7755969d4e70eabfacb6ef403e887cc0be90b789f6d9c59039c6c73
+size 163618
diff --git a/t2/task_image/04_05/test_04_05.png b/t2/task_image/04_05/test_04_05.png
new file mode 100644
index 0000000000000000000000000000000000000000..d671ede6ffee2893230e3974bab6e4769ff2f6a2
--- /dev/null
+++ b/t2/task_image/04_05/test_04_05.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f352a36ed0b817f961a7874a548bfd23fda31dcc941bb6be59a9f7ac7925472d
+size 15512
diff --git a/t2/task_image/04_06/04_06.txt b/t2/task_image/04_06/04_06.txt
new file mode 100644
index 0000000000000000000000000000000000000000..a82f282d35d24c7a10ca7a17122e6d8f398aa843
--- /dev/null
+++ b/t2/task_image/04_06/04_06.txt
@@ -0,0 +1,89 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image and motion reference frames, 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:
+04_06
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task_image/04_06/test_04_06.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t2/task_image/04_06/frame/04_06_000.png, /xxx/ExeWorldBench/t2/task_image/04_06/frame/04_06_001.png, /xxx/ExeWorldBench/t2/task_image/04_06/frame/04_06_002.png, /xxx/ExeWorldBench/t2/task_image/04_06/frame/04_06_003.png, /xxx/ExeWorldBench/t2/task_image/04_06/frame/04_06_004.png
+
+Use only the reference image and motion reference frames 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_image/04_06
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task_image/04_06. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given:
+
+1. A visual reference image of a multi-stage mechanical chain.
+2. A sequence of ordered motion reference frames illustrating how the mechanical chain is approximately intended to operate.
+
+Both the reference image and the motion frames provide approximate visual guidance rather than an exact executable specification.
+
+The reference image mainly indicates the mechanical components involved and their approximate spatial arrangement, while the motion frames provide additional cues about the approximate motion, interaction, and progression of the mechanical chain.
+
+The exact positions, distances, orientations, trajectories, timing, and geometric relationships shown in these visual references may not directly form a physically executable system.
+
+Your task is to reason about how the components should mechanically interact, infer the intended chain behavior from the visual references, adjust the spatial configuration and motion details 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 visual references, but to construct a physically executable mechanical system in which the initial action propagates through all stages and produces the intended chain reaction through realistic physical interactions.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure indicated by the visual references.
+- Use the ordered motion frames as approximate cues to infer the intended motion direction, stage order, component interactions, and causal progression of the chain.
+- The visual references should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, trajectories, or other geometric and motion 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.
+- The provided motion frames are approximate behavioral references, not target poses or trajectories to be directly reproduced.
+- Do not directly prescribe the per-frame position or rotation of components to imitate the provided motion frames.
+- 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, isolated poses, 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 generated motion should follow the overall behavioral progression indicated by the visual references while remaining physically executable.
+- The animation must be long enough to show the complete mechanical chain.
+- An implementation that only visually matches several reference frames but fails to produce a continuous physical chain between them is considered incomplete.
+- 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 references 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_image/04_06/04_06.py
+* /xxx/ExeWorldBench/t2/task_image/04_06/04_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.
diff --git a/t2/task_image/04_06/frame/04_06_000.png b/t2/task_image/04_06/frame/04_06_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..f90a8d08a433e0d44194f65dd2208f2db0bf9e73
--- /dev/null
+++ b/t2/task_image/04_06/frame/04_06_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:26a5320660a0330b98bf9c50a54a73b06842c4ee151fbafe69cae6fae105b605
+size 149807
diff --git a/t2/task_image/04_06/frame/04_06_001.png b/t2/task_image/04_06/frame/04_06_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..dc09913e381b629694bceb3b9773322c9863b08e
--- /dev/null
+++ b/t2/task_image/04_06/frame/04_06_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d8c111a202b80314d701562feac4693f0498a2f7ab9af5eb5ed03683be8bde60
+size 152721
diff --git a/t2/task_image/04_06/frame/04_06_002.png b/t2/task_image/04_06/frame/04_06_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..f2a853f90c1452742109812636a4b46fb8fb2061
--- /dev/null
+++ b/t2/task_image/04_06/frame/04_06_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fb4738d48696dabcbffdc9c6c4424546a9041127e34bf96bda8671295f04829f
+size 155375
diff --git a/t2/task_image/04_06/frame/04_06_003.png b/t2/task_image/04_06/frame/04_06_003.png
new file mode 100644
index 0000000000000000000000000000000000000000..f03fab3d93103e4aa28f0ce745ec2095b4915d59
--- /dev/null
+++ b/t2/task_image/04_06/frame/04_06_003.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7dc951e5c76925440a45a49d99d1736caac8cbcee3fdc975cbf92a98f4ac4a34
+size 156551
diff --git a/t2/task_image/04_06/frame/04_06_004.png b/t2/task_image/04_06/frame/04_06_004.png
new file mode 100644
index 0000000000000000000000000000000000000000..9cd6f8e4a4facca97b8e4500af7f1f17681fd86c
--- /dev/null
+++ b/t2/task_image/04_06/frame/04_06_004.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b2f749bb8d6a612848a61d7b56f338e90837c0943d35db95f322e42aed8d2679
+size 156515
diff --git a/t2/task_image/04_06/test_04_06.png b/t2/task_image/04_06/test_04_06.png
new file mode 100644
index 0000000000000000000000000000000000000000..d9977ca7a5838bf0e65734678a5faf030b091a25
--- /dev/null
+++ b/t2/task_image/04_06/test_04_06.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bc28a6b85d8474ec0a391634963a9af31c22794919970219a57ccecb88ad85be
+size 14659
diff --git a/t2/task_image/04_07/04_07.txt b/t2/task_image/04_07/04_07.txt
new file mode 100644
index 0000000000000000000000000000000000000000..ef6185bca975bdebbae290fa8eea72102662fee1
--- /dev/null
+++ b/t2/task_image/04_07/04_07.txt
@@ -0,0 +1,89 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image and motion reference frames, 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:
+04_07
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task_image/04_07/test_04_07.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t2/task_image/04_07/frame/04_07_000.png, /xxx/ExeWorldBench/t2/task_image/04_07/frame/04_07_001.png, /xxx/ExeWorldBench/t2/task_image/04_07/frame/04_07_002.png, /xxx/ExeWorldBench/t2/task_image/04_07/frame/04_07_003.png, /xxx/ExeWorldBench/t2/task_image/04_07/frame/04_07_004.png
+
+Use only the reference image and motion reference frames 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_image/04_07
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task_image/04_07. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given:
+
+1. A visual reference image of a multi-stage mechanical chain.
+2. A sequence of ordered motion reference frames illustrating how the mechanical chain is approximately intended to operate.
+
+Both the reference image and the motion frames provide approximate visual guidance rather than an exact executable specification.
+
+The reference image mainly indicates the mechanical components involved and their approximate spatial arrangement, while the motion frames provide additional cues about the approximate motion, interaction, and progression of the mechanical chain.
+
+The exact positions, distances, orientations, trajectories, timing, and geometric relationships shown in these visual references may not directly form a physically executable system.
+
+Your task is to reason about how the components should mechanically interact, infer the intended chain behavior from the visual references, adjust the spatial configuration and motion details 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 visual references, but to construct a physically executable mechanical system in which the initial action propagates through all stages and produces the intended chain reaction through realistic physical interactions.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure indicated by the visual references.
+- Use the ordered motion frames as approximate cues to infer the intended motion direction, stage order, component interactions, and causal progression of the chain.
+- The visual references should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, trajectories, or other geometric and motion 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.
+- The provided motion frames are approximate behavioral references, not target poses or trajectories to be directly reproduced.
+- Do not directly prescribe the per-frame position or rotation of components to imitate the provided motion frames.
+- 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, isolated poses, 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 generated motion should follow the overall behavioral progression indicated by the visual references while remaining physically executable.
+- The animation must be long enough to show the complete mechanical chain.
+- An implementation that only visually matches several reference frames but fails to produce a continuous physical chain between them is considered incomplete.
+- 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 references 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_image/04_07/04_07.py
+* /xxx/ExeWorldBench/t2/task_image/04_07/04_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.
diff --git a/t2/task_image/04_07/frame/04_07_000.png b/t2/task_image/04_07/frame/04_07_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..87b504c875e75c60fee8cc81de099941fc6da2c1
--- /dev/null
+++ b/t2/task_image/04_07/frame/04_07_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a52a73c32fe3a9b6fc6f575b97cad3faa676b7467395f21d426a315981872e43
+size 145042
diff --git a/t2/task_image/04_07/frame/04_07_001.png b/t2/task_image/04_07/frame/04_07_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..25278340b9c63eea1a711ab6cd67f19c894cbb82
--- /dev/null
+++ b/t2/task_image/04_07/frame/04_07_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:87b136c5a050b8045edd6bc5ca9afd7fe4de8ceaa0f12b4c2e8cf0b8b9bd1009
+size 150003
diff --git a/t2/task_image/04_07/frame/04_07_002.png b/t2/task_image/04_07/frame/04_07_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..02c7565d811391f8b5d7976c6d54817cb5891dc2
--- /dev/null
+++ b/t2/task_image/04_07/frame/04_07_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:35aa126ab11fd93d6b53e0020f69febd547188f0cf5396f7198d75ead23e0166
+size 150276
diff --git a/t2/task_image/04_07/frame/04_07_003.png b/t2/task_image/04_07/frame/04_07_003.png
new file mode 100644
index 0000000000000000000000000000000000000000..b01c80c3a3821d207842252e293604a984793e60
--- /dev/null
+++ b/t2/task_image/04_07/frame/04_07_003.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a6ba91ae59846bf6a4ae9092242862be7dc02d4f63f7a9711d0ac37ea792dc24
+size 150377
diff --git a/t2/task_image/04_07/frame/04_07_004.png b/t2/task_image/04_07/frame/04_07_004.png
new file mode 100644
index 0000000000000000000000000000000000000000..d0ed100c2d7b5250dcf707b46c55d999b9f02102
--- /dev/null
+++ b/t2/task_image/04_07/frame/04_07_004.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5e7f8924d758233d45a8e8969e3e6899871afbd318f52e1d3071618081df382d
+size 150901
diff --git a/t2/task_image/04_07/test_04_07.png b/t2/task_image/04_07/test_04_07.png
new file mode 100644
index 0000000000000000000000000000000000000000..dfa16378506539e0018c2f14a5a5c3ab5d69e769
--- /dev/null
+++ b/t2/task_image/04_07/test_04_07.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8879d15aa758178f6a5593021a9e6d3b4c75c92f97e563183afdf7e5d1d36118
+size 15860
diff --git a/t2/task_image/04_08/04_08.txt b/t2/task_image/04_08/04_08.txt
new file mode 100644
index 0000000000000000000000000000000000000000..ac4774c1af03e9fbc96517d867d8f471b9b34d79
--- /dev/null
+++ b/t2/task_image/04_08/04_08.txt
@@ -0,0 +1,89 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image and motion reference frames, 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:
+04_08
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task_image/04_08/test_04_08.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t2/task_image/04_08/frame/04_08_000.png, /xxx/ExeWorldBench/t2/task_image/04_08/frame/04_08_001.png, /xxx/ExeWorldBench/t2/task_image/04_08/frame/04_08_002.png, /xxx/ExeWorldBench/t2/task_image/04_08/frame/04_08_003.png, /xxx/ExeWorldBench/t2/task_image/04_08/frame/04_08_004.png
+
+Use only the reference image and motion reference frames 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_image/04_08
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task_image/04_08. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given:
+
+1. A visual reference image of a multi-stage mechanical chain.
+2. A sequence of ordered motion reference frames illustrating how the mechanical chain is approximately intended to operate.
+
+Both the reference image and the motion frames provide approximate visual guidance rather than an exact executable specification.
+
+The reference image mainly indicates the mechanical components involved and their approximate spatial arrangement, while the motion frames provide additional cues about the approximate motion, interaction, and progression of the mechanical chain.
+
+The exact positions, distances, orientations, trajectories, timing, and geometric relationships shown in these visual references may not directly form a physically executable system.
+
+Your task is to reason about how the components should mechanically interact, infer the intended chain behavior from the visual references, adjust the spatial configuration and motion details 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 visual references, but to construct a physically executable mechanical system in which the initial action propagates through all stages and produces the intended chain reaction through realistic physical interactions.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure indicated by the visual references.
+- Use the ordered motion frames as approximate cues to infer the intended motion direction, stage order, component interactions, and causal progression of the chain.
+- The visual references should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, trajectories, or other geometric and motion 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.
+- The provided motion frames are approximate behavioral references, not target poses or trajectories to be directly reproduced.
+- Do not directly prescribe the per-frame position or rotation of components to imitate the provided motion frames.
+- 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, isolated poses, 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 generated motion should follow the overall behavioral progression indicated by the visual references while remaining physically executable.
+- The animation must be long enough to show the complete mechanical chain.
+- An implementation that only visually matches several reference frames but fails to produce a continuous physical chain between them is considered incomplete.
+- 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 references 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_image/04_08/04_08.py
+* /xxx/ExeWorldBench/t2/task_image/04_08/04_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.
diff --git a/t2/task_image/04_08/frame/04_08_000.png b/t2/task_image/04_08/frame/04_08_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..315bca325360404b64b65623543e388ea14c628d
--- /dev/null
+++ b/t2/task_image/04_08/frame/04_08_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9e1885c2595846523b8e69fe12b4a6f6bc0fc8e2effbe3d77ba79255bf54e222
+size 176941
diff --git a/t2/task_image/04_08/frame/04_08_001.png b/t2/task_image/04_08/frame/04_08_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..b230b441b836825c4a524f57853be162ee02ccab
--- /dev/null
+++ b/t2/task_image/04_08/frame/04_08_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f302fb995ff45ccd618883b0f326d9fa1548e06d7db4ed0d11343e594a98cf56
+size 177507
diff --git a/t2/task_image/04_08/frame/04_08_002.png b/t2/task_image/04_08/frame/04_08_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..42ed9eb27104c6a7e9319399373d83c46f317a5b
--- /dev/null
+++ b/t2/task_image/04_08/frame/04_08_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f7a940f0fc897eec9cc16ecc0bb7a8ea5f5d0df87c25651771307ea46488f69e
+size 179942
diff --git a/t2/task_image/04_08/frame/04_08_003.png b/t2/task_image/04_08/frame/04_08_003.png
new file mode 100644
index 0000000000000000000000000000000000000000..487864a8e352be67b45c9e58e222802a2a1e328a
--- /dev/null
+++ b/t2/task_image/04_08/frame/04_08_003.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:502d823aa78ca37e55f301ac290ae7e90daa0732b26387affb4ec4b69aa299ae
+size 180615
diff --git a/t2/task_image/04_08/frame/04_08_004.png b/t2/task_image/04_08/frame/04_08_004.png
new file mode 100644
index 0000000000000000000000000000000000000000..8d51604df56404da677124d0b7e82325f885cdaa
--- /dev/null
+++ b/t2/task_image/04_08/frame/04_08_004.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9fa91b92724487150acd0dbbb6d00def5c1db674f3d4f36987f0e59e3140ba87
+size 179074
diff --git a/t2/task_image/04_08/test_04_08.png b/t2/task_image/04_08/test_04_08.png
new file mode 100644
index 0000000000000000000000000000000000000000..7decf9087eb0f611b86c6a3f7dd4e2e042014fdf
--- /dev/null
+++ b/t2/task_image/04_08/test_04_08.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cafcb33032ad12f845f1572122a55f3a7498548acd81c61e4d5f4d60dd90551e
+size 16369
diff --git a/t2/task_image/04_09/04_09.txt b/t2/task_image/04_09/04_09.txt
new file mode 100644
index 0000000000000000000000000000000000000000..7579b6faae70847b4629524155e6cb51a762549d
--- /dev/null
+++ b/t2/task_image/04_09/04_09.txt
@@ -0,0 +1,89 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image and motion reference frames, 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:
+04_09
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task_image/04_09/test_04_09.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t2/task_image/04_09/frame/04_09_000.png, /xxx/ExeWorldBench/t2/task_image/04_09/frame/04_09_001.png, /xxx/ExeWorldBench/t2/task_image/04_09/frame/04_09_002.png, /xxx/ExeWorldBench/t2/task_image/04_09/frame/04_09_003.png, /xxx/ExeWorldBench/t2/task_image/04_09/frame/04_09_004.png
+
+Use only the reference image and motion reference frames 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_image/04_09
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task_image/04_09. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given:
+
+1. A visual reference image of a multi-stage mechanical chain.
+2. A sequence of ordered motion reference frames illustrating how the mechanical chain is approximately intended to operate.
+
+Both the reference image and the motion frames provide approximate visual guidance rather than an exact executable specification.
+
+The reference image mainly indicates the mechanical components involved and their approximate spatial arrangement, while the motion frames provide additional cues about the approximate motion, interaction, and progression of the mechanical chain.
+
+The exact positions, distances, orientations, trajectories, timing, and geometric relationships shown in these visual references may not directly form a physically executable system.
+
+Your task is to reason about how the components should mechanically interact, infer the intended chain behavior from the visual references, adjust the spatial configuration and motion details 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 visual references, but to construct a physically executable mechanical system in which the initial action propagates through all stages and produces the intended chain reaction through realistic physical interactions.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure indicated by the visual references.
+- Use the ordered motion frames as approximate cues to infer the intended motion direction, stage order, component interactions, and causal progression of the chain.
+- The visual references should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, trajectories, or other geometric and motion 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.
+- The provided motion frames are approximate behavioral references, not target poses or trajectories to be directly reproduced.
+- Do not directly prescribe the per-frame position or rotation of components to imitate the provided motion frames.
+- 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, isolated poses, 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 generated motion should follow the overall behavioral progression indicated by the visual references while remaining physically executable.
+- The animation must be long enough to show the complete mechanical chain.
+- An implementation that only visually matches several reference frames but fails to produce a continuous physical chain between them is considered incomplete.
+- 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 references 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_image/04_09/04_09.py
+* /xxx/ExeWorldBench/t2/task_image/04_09/04_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.
diff --git a/t2/task_image/04_09/frame/04_09_000.png b/t2/task_image/04_09/frame/04_09_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..47de75432965bc4b7dc75b0473b84368b8bc7fd1
--- /dev/null
+++ b/t2/task_image/04_09/frame/04_09_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4c260d4cda94c294860ca98aa2388a75ca5fc921b469ad95f2f1725a51c6a782
+size 140827
diff --git a/t2/task_image/04_09/frame/04_09_001.png b/t2/task_image/04_09/frame/04_09_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..354e7c7ebc0a2a9f20f97baa455147e060f20104
--- /dev/null
+++ b/t2/task_image/04_09/frame/04_09_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cb67d2ed14fd346fb8e0499d92fe3678ec11f6c7bffc604a0417a8b2ebbe5709
+size 146078
diff --git a/t2/task_image/04_09/frame/04_09_002.png b/t2/task_image/04_09/frame/04_09_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..fdec4ae107151828b4f48a17c6b6b5690aff7c24
--- /dev/null
+++ b/t2/task_image/04_09/frame/04_09_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e193b2f66dd1e035dc24c43f11aa8e5e37c059fff7ea552885fcffb14dcdc0fc
+size 150671
diff --git a/t2/task_image/04_09/frame/04_09_003.png b/t2/task_image/04_09/frame/04_09_003.png
new file mode 100644
index 0000000000000000000000000000000000000000..71e4e1e5fbdde5e08563d00b66eace9056b49683
--- /dev/null
+++ b/t2/task_image/04_09/frame/04_09_003.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9fe269bad607e6685d02ec349e9982d4d2812512b2ce2143e919ba1aa693ab19
+size 152203
diff --git a/t2/task_image/04_09/frame/04_09_004.png b/t2/task_image/04_09/frame/04_09_004.png
new file mode 100644
index 0000000000000000000000000000000000000000..61d5097d11895e8b863e8064ef399268af4c3b0b
--- /dev/null
+++ b/t2/task_image/04_09/frame/04_09_004.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a89a1d4ace326aecc73fca1d6a37783fb9e367fabbb64736b57eb40f81cc6391
+size 152601
diff --git a/t2/task_image/04_09/test_04_09.png b/t2/task_image/04_09/test_04_09.png
new file mode 100644
index 0000000000000000000000000000000000000000..419792d8cb91b36e0dfb71f7193e8bbee0456805
--- /dev/null
+++ b/t2/task_image/04_09/test_04_09.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:526b1ab64c1d613e7b34b1a0f121e5ddc9edf7a641c8be6ad2c06677e4791381
+size 13461
diff --git a/t2/task_image/04_10/04_10.txt b/t2/task_image/04_10/04_10.txt
new file mode 100644
index 0000000000000000000000000000000000000000..e89f14227817f2d3f297772a38d83a6aab0d3d26
--- /dev/null
+++ b/t2/task_image/04_10/04_10.txt
@@ -0,0 +1,89 @@
+You are an autonomous Codex agent with access to the local filesystem, shell,
+the reference image and motion reference frames, 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:
+04_10
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task_image/04_10/test_04_10.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t2/task_image/04_10/frame/04_10_000.png, /xxx/ExeWorldBench/t2/task_image/04_10/frame/04_10_001.png, /xxx/ExeWorldBench/t2/task_image/04_10/frame/04_10_002.png, /xxx/ExeWorldBench/t2/task_image/04_10/frame/04_10_003.png, /xxx/ExeWorldBench/t2/task_image/04_10/frame/04_10_004.png
+
+Use only the reference image and motion reference frames 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_image/04_10
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task_image/04_10. Temporary files may be created elsewhere only when necessary and must be removed before completion.
+
+==================================================
+TASK
+==================================================
+
+You are given:
+
+1. A visual reference image of a multi-stage mechanical chain.
+2. A sequence of ordered motion reference frames illustrating how the mechanical chain is approximately intended to operate.
+
+Both the reference image and the motion frames provide approximate visual guidance rather than an exact executable specification.
+
+The reference image mainly indicates the mechanical components involved and their approximate spatial arrangement, while the motion frames provide additional cues about the approximate motion, interaction, and progression of the mechanical chain.
+
+The exact positions, distances, orientations, trajectories, timing, and geometric relationships shown in these visual references may not directly form a physically executable system.
+
+Your task is to reason about how the components should mechanically interact, infer the intended chain behavior from the visual references, adjust the spatial configuration and motion details 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 visual references, but to construct a physically executable mechanical system in which the initial action propagates through all stages and produces the intended chain reaction through realistic physical interactions.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Compositional Mechanical Reasoning
+
+- The reconstructed system must preserve the major mechanical components and overall mechanical structure indicated by the visual references.
+- Use the ordered motion frames as approximate cues to infer the intended motion direction, stage order, component interactions, and causal progression of the chain.
+- The visual references should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- To make the complete mechanical chain physically executable, you may adjust component positions, distances, orientations, heights, trajectories, or other geometric and motion 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.
+- The provided motion frames are approximate behavioral references, not target poses or trajectories to be directly reproduced.
+- Do not directly prescribe the per-frame position or rotation of components to imitate the provided motion frames.
+- 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, isolated poses, 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 generated motion should follow the overall behavioral progression indicated by the visual references while remaining physically executable.
+- The animation must be long enough to show the complete mechanical chain.
+- An implementation that only visually matches several reference frames but fails to produce a continuous physical chain between them is considered incomplete.
+- 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 references 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_image/04_10/04_10.py
+* /xxx/ExeWorldBench/t2/task_image/04_10/04_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.
diff --git a/t2/task_image/04_10/frame/04_10_000.png b/t2/task_image/04_10/frame/04_10_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..3357151de26afcda52e4ab2b892d94191d887e69
--- /dev/null
+++ b/t2/task_image/04_10/frame/04_10_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8fe1d96784f5e948c55a54ed8493e474ba5a825e1d9902395d5b687068665aa5
+size 141416
diff --git a/t2/task_image/04_10/frame/04_10_001.png b/t2/task_image/04_10/frame/04_10_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..d85201920430284836147543bcaaf1dd0e95dfcb
--- /dev/null
+++ b/t2/task_image/04_10/frame/04_10_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:216c68d5d6f57bd7c85502d63ec25db38ba836321b087214cca4d42b992de18e
+size 146592