diff --git a/t1/task_image/003/frame/003_002.png b/t1/task_image/003/frame/003_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..2804aa184b819985710608f9eb6a75e3f35ee632
--- /dev/null
+++ b/t1/task_image/003/frame/003_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:253e0286b80f7df4925e3d5c04963e3e9a0fa00ead5f370b56457d8e4c77f4d3
+size 8224
diff --git a/t1/task_image/004/004.png b/t1/task_image/004/004.png
new file mode 100644
index 0000000000000000000000000000000000000000..fc8ba83ecaddd1e58095ae51dab62b84b306bc30
--- /dev/null
+++ b/t1/task_image/004/004.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:36551f4ae45a693d391b72b1d51a1c3917f9db1bc6785705d49596a485db59c9
+size 42539
diff --git a/t1/task_image/004/004.txt b/t1/task_image/004/004.txt
new file mode 100644
index 0000000000000000000000000000000000000000..847bba2056748624e53392566898ff7fb8a77136
--- /dev/null
+++ b/t1/task_image/004/004.txt
@@ -0,0 +1,82 @@
+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:
+004
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/004/004.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/004/frame/004_000.png, /xxx/ExeWorldBench/t1/task_image/004/frame/004_001.png, /xxx/ExeWorldBench/t1/task_image/004/frame/004_002.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/t1/task_image/004
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/004. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/004/004.py
+* /xxx/ExeWorldBench/t1/task_image/004/004.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/t1/task_image/004/frame/004_000.png b/t1/task_image/004/frame/004_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..9b197c28ddc99fb6f5bb09ae38c8f8a207d51c2a
--- /dev/null
+++ b/t1/task_image/004/frame/004_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:35fc784f00da9574d65dad52e7888856a96f326c75c30f8c985f477d04d80485
+size 8402
diff --git a/t1/task_image/004/frame/004_001.png b/t1/task_image/004/frame/004_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..1755f42fac4f49f644a55d35609d1fc0e6a275df
--- /dev/null
+++ b/t1/task_image/004/frame/004_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6ea7da40795bd08a21e488042b73742076ec6341c41dbc51765c33303c45b758
+size 8667
diff --git a/t1/task_image/004/frame/004_002.png b/t1/task_image/004/frame/004_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..50416163b04df5a7614d8afa67cb5be45c7bd969
--- /dev/null
+++ b/t1/task_image/004/frame/004_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f83c89b0fc76dcaa9846f1a1f5f3ff7c65670987d4caed9c296274dc6b929e0d
+size 8426
diff --git a/t1/task_image/005/005.png b/t1/task_image/005/005.png
new file mode 100644
index 0000000000000000000000000000000000000000..1fdb4b6d2d00bc9157b278f1efc133a82969d779
--- /dev/null
+++ b/t1/task_image/005/005.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fd3fdbcef0def6736d1d6e76554b327358f878aad49d853cbee51577a13f8664
+size 24926
diff --git a/t1/task_image/005/005.txt b/t1/task_image/005/005.txt
new file mode 100644
index 0000000000000000000000000000000000000000..174af6acd955078e6482cae79b9e0f07c3f5be12
--- /dev/null
+++ b/t1/task_image/005/005.txt
@@ -0,0 +1,82 @@
+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:
+005
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/005/005.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/005/frame/005_000.png, /xxx/ExeWorldBench/t1/task_image/005/frame/005_001.png, /xxx/ExeWorldBench/t1/task_image/005/frame/005_002.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/t1/task_image/005
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/005. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/005/005.py
+* /xxx/ExeWorldBench/t1/task_image/005/005.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/t1/task_image/005/frame/005_000.png b/t1/task_image/005/frame/005_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..543a3b5ce5afa7e58cf129f1dc06a1523524507d
--- /dev/null
+++ b/t1/task_image/005/frame/005_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:66b76d8e40185e1d4fbc85850fd95cfce224a93f026dba57ce2c6504022be206
+size 5171
diff --git a/t1/task_image/005/frame/005_001.png b/t1/task_image/005/frame/005_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..2f6d59e86b17480baa01575957dcf5618ee6de51
--- /dev/null
+++ b/t1/task_image/005/frame/005_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3576062a44973d5bb49a29090af3b629683e1e2d48320a67b6d0373778a349eb
+size 4835
diff --git a/t1/task_image/005/frame/005_002.png b/t1/task_image/005/frame/005_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..b77dbd7fb33d7e1719520adac664f5948ad1cc45
--- /dev/null
+++ b/t1/task_image/005/frame/005_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:67f8c57936b557f628b503d4987dfcf2701567a331c365e76c78d1f9ef0159b0
+size 5014
diff --git a/t1/task_image/006/006.png b/t1/task_image/006/006.png
new file mode 100644
index 0000000000000000000000000000000000000000..63d9dedde1ee9b1179f2e237722c95b8b4562654
--- /dev/null
+++ b/t1/task_image/006/006.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fb657ea0f262f7aca4cbcca1312d2b5f26299fec84a82df1cbfc592cb473ffcb
+size 31434
diff --git a/t1/task_image/006/006.txt b/t1/task_image/006/006.txt
new file mode 100644
index 0000000000000000000000000000000000000000..f351e447edfb178dbb8651c8186bd3de34256798
--- /dev/null
+++ b/t1/task_image/006/006.txt
@@ -0,0 +1,82 @@
+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:
+006
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/006/006.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/006/frame/006_000.png, /xxx/ExeWorldBench/t1/task_image/006/frame/006_001.png, /xxx/ExeWorldBench/t1/task_image/006/frame/006_002.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/t1/task_image/006
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/006. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/006/006.py
+* /xxx/ExeWorldBench/t1/task_image/006/006.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/t1/task_image/006/frame/006_000.png b/t1/task_image/006/frame/006_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..12a195004090b42023872956d9da6317abb77dcc
--- /dev/null
+++ b/t1/task_image/006/frame/006_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:20f7458ca52fbf02e2da2b770aa8692faa683f9df0c1b17eb24e6dcee9267993
+size 5360
diff --git a/t1/task_image/006/frame/006_001.png b/t1/task_image/006/frame/006_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..82db22199f624c56a17fbbf38fb6f807d291f1cf
--- /dev/null
+++ b/t1/task_image/006/frame/006_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:13775e79836b7096c2b5c7a3b3592ab75527e12a92889eb3c85e5e02eb62c2e8
+size 5596
diff --git a/t1/task_image/006/frame/006_002.png b/t1/task_image/006/frame/006_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..1da858748d70090fbdd94ab2493da35634f63afc
--- /dev/null
+++ b/t1/task_image/006/frame/006_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e620d35139a09fe0c4879273fd20fa18431adf1560e9b0d49600adaf1e4dc152
+size 5909
diff --git a/t1/task_image/007/007.png b/t1/task_image/007/007.png
new file mode 100644
index 0000000000000000000000000000000000000000..fe393f98e6775e09dc6f6cd1fa008778bb975e6d
--- /dev/null
+++ b/t1/task_image/007/007.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:41e15d1f2fd114fabacf99a51ef94ad8e6fd53734ccaf107685e25faffb9195e
+size 24546
diff --git a/t1/task_image/007/007.txt b/t1/task_image/007/007.txt
new file mode 100644
index 0000000000000000000000000000000000000000..b3b0bbd62f8460ac7e07a29f4557b7c5b78f5977
--- /dev/null
+++ b/t1/task_image/007/007.txt
@@ -0,0 +1,82 @@
+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:
+007
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/007/007.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/007/frame/007_000.png, /xxx/ExeWorldBench/t1/task_image/007/frame/007_001.png, /xxx/ExeWorldBench/t1/task_image/007/frame/007_002.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/t1/task_image/007
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/007. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/007/007.py
+* /xxx/ExeWorldBench/t1/task_image/007/007.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/t1/task_image/007/frame/007_000.png b/t1/task_image/007/frame/007_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..4a9f237928b02ec7556ae34f4132759532bf2141
--- /dev/null
+++ b/t1/task_image/007/frame/007_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:05a89e328609a12cecee38abf6f1e4a4dcb261466fa4cb1292966f8c0aed7635
+size 5234
diff --git a/t1/task_image/007/frame/007_001.png b/t1/task_image/007/frame/007_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..b889c2a9ac8646cc87b9a267882e836c557b391a
--- /dev/null
+++ b/t1/task_image/007/frame/007_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cc002e3874ddce0df0f1ff8983f026e82d32b5cd0dcbc63d700231ff8153ed7a
+size 5616
diff --git a/t1/task_image/007/frame/007_002.png b/t1/task_image/007/frame/007_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..d90d0d9b620df8efa69ce79404c3ab0bcd808712
--- /dev/null
+++ b/t1/task_image/007/frame/007_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6959b2d4e3ce8647a8e73708b0a24247315da77ca6ae7529bc9f9bff716324af
+size 5161
diff --git a/t1/task_image/008/008.png b/t1/task_image/008/008.png
new file mode 100644
index 0000000000000000000000000000000000000000..27542eddefe5789c9192530b572dbcbf4ee3e770
--- /dev/null
+++ b/t1/task_image/008/008.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8557df2b783d4de11fba702575564f3a11a47c2c865b6fedf6e11cb637db7a24
+size 15367
diff --git a/t1/task_image/008/008.txt b/t1/task_image/008/008.txt
new file mode 100644
index 0000000000000000000000000000000000000000..7bd0f6ea96349a3c60c151805062e3666689a881
--- /dev/null
+++ b/t1/task_image/008/008.txt
@@ -0,0 +1,82 @@
+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:
+008
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/008/008.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/008/frame/008_000.png, /xxx/ExeWorldBench/t1/task_image/008/frame/008_001.png, /xxx/ExeWorldBench/t1/task_image/008/frame/008_002.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/t1/task_image/008
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/008. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/008/008.py
+* /xxx/ExeWorldBench/t1/task_image/008/008.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/t1/task_image/008/frame/008_000.png b/t1/task_image/008/frame/008_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..e584ca1850f3ea5691d0c478b02e852020a6734a
--- /dev/null
+++ b/t1/task_image/008/frame/008_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:320b8064c84f0b14b55bceae91afb5c943aab326f479adf407d185245bc181f5
+size 4475
diff --git a/t1/task_image/008/frame/008_001.png b/t1/task_image/008/frame/008_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..9a3f1613f65c0982f1c41e98ead7157d1ef1cc68
--- /dev/null
+++ b/t1/task_image/008/frame/008_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2fb56a3d2c6e97cc20636495b3318d2beef975ee7ec767ef0e3f71a06e082518
+size 4469
diff --git a/t1/task_image/008/frame/008_002.png b/t1/task_image/008/frame/008_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..a7860db69ae6d1925aabb5e694caa86dc3f548d3
--- /dev/null
+++ b/t1/task_image/008/frame/008_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fd4ac5872674faa36fb4cff4f8e5f9e3aadc70eceaf5c522fcd7a4fe7c61dec2
+size 4442
diff --git a/t1/task_image/009/009.png b/t1/task_image/009/009.png
new file mode 100644
index 0000000000000000000000000000000000000000..e5aa01b745a2cad85d704bf4d589708ba444459f
--- /dev/null
+++ b/t1/task_image/009/009.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2864bfdbd8c9b0aa38fa760b0070d16f1a32c5b678a174ad91475e5918cbc898
+size 140529
diff --git a/t1/task_image/009/009.txt b/t1/task_image/009/009.txt
new file mode 100644
index 0000000000000000000000000000000000000000..aa9d7b58b75ff9f795efa5af09b4d23ea41c6a96
--- /dev/null
+++ b/t1/task_image/009/009.txt
@@ -0,0 +1,82 @@
+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:
+009
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/009/009.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/009/frame/009_000.png, /xxx/ExeWorldBench/t1/task_image/009/frame/009_001.png, /xxx/ExeWorldBench/t1/task_image/009/frame/009_002.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/t1/task_image/009
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/009. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/009/009.py
+* /xxx/ExeWorldBench/t1/task_image/009/009.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/t1/task_image/009/frame/009_000.png b/t1/task_image/009/frame/009_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..39b735f668e54db57a5af1ad5b7692940eac578e
--- /dev/null
+++ b/t1/task_image/009/frame/009_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bfb365c3b267dc5dde01fe96c795a1926702ba56da033d0005b23b5dafe04a06
+size 20023
diff --git a/t1/task_image/009/frame/009_001.png b/t1/task_image/009/frame/009_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..2c267bff7d213f3274e1cd291ec32f82b0ada1c3
--- /dev/null
+++ b/t1/task_image/009/frame/009_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2aee39327a5a6492b60fe003f9496d9a54d974379ff80fe815da5167ffa64ad2
+size 20093
diff --git a/t1/task_image/009/frame/009_002.png b/t1/task_image/009/frame/009_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..ef3a65411a2b387e7270d6ee2c7e469d61e21687
--- /dev/null
+++ b/t1/task_image/009/frame/009_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3017f0c39bcfe6e303e36c557797abf4dd48f9f8e56f6bcb29a0f5c347abbb4f
+size 20385
diff --git a/t1/task_image/010/010.png b/t1/task_image/010/010.png
new file mode 100644
index 0000000000000000000000000000000000000000..1a5c0a3a285b3afa1d70cf2eb264b0da11426c66
--- /dev/null
+++ b/t1/task_image/010/010.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b2e457c73b5766fd784c4483ac5a7507f4f5083db051f286196a68f6356ae0f7
+size 56870
diff --git a/t1/task_image/010/010.txt b/t1/task_image/010/010.txt
new file mode 100644
index 0000000000000000000000000000000000000000..3ae225e727de5b0012907d8ffc2cb73553595f95
--- /dev/null
+++ b/t1/task_image/010/010.txt
@@ -0,0 +1,82 @@
+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:
+010
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/010/010.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/010/frame/010_000.png, /xxx/ExeWorldBench/t1/task_image/010/frame/010_001.png, /xxx/ExeWorldBench/t1/task_image/010/frame/010_002.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/t1/task_image/010
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/010. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/010/010.py
+* /xxx/ExeWorldBench/t1/task_image/010/010.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/t1/task_image/010/frame/010_000.png b/t1/task_image/010/frame/010_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..fdb4a5a5e5f6a6e23b0471f2ce696cdc10f4d242
--- /dev/null
+++ b/t1/task_image/010/frame/010_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:959f9168b0b7d3673a986fa02cb7cb3ed14c3b505b9ccc12bb3361cc5a28dd75
+size 8828
diff --git a/t1/task_image/010/frame/010_001.png b/t1/task_image/010/frame/010_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..fbffa748cf4e6ae006b672482c110e2e812f25a4
--- /dev/null
+++ b/t1/task_image/010/frame/010_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d43c7e5cef009a059f03c12fe136f7cd781e3029740133de913da7fce852e0db
+size 9137
diff --git a/t1/task_image/010/frame/010_002.png b/t1/task_image/010/frame/010_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..36fc9e858d0bce9b71490315d0d3d235923c5989
--- /dev/null
+++ b/t1/task_image/010/frame/010_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:372fbcfda2f8b11d306d28306bd7704477450daf4c6e76a638868e459771ad74
+size 9032
diff --git a/t1/task_image/011/011.png b/t1/task_image/011/011.png
new file mode 100644
index 0000000000000000000000000000000000000000..9aa77c038ca5d200770bfd94984cda1c10a8c3cb
--- /dev/null
+++ b/t1/task_image/011/011.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5bef5abcf9256a506e5f17838088349510f544705ef131de5ac1b98c237ced3a
+size 31570
diff --git a/t1/task_image/011/011.txt b/t1/task_image/011/011.txt
new file mode 100644
index 0000000000000000000000000000000000000000..66de042619049c72ca12cb23e6a2a53537ed1444
--- /dev/null
+++ b/t1/task_image/011/011.txt
@@ -0,0 +1,82 @@
+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:
+011
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/011/011.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/011/frame/011_000.png, /xxx/ExeWorldBench/t1/task_image/011/frame/011_001.png, /xxx/ExeWorldBench/t1/task_image/011/frame/011_002.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/t1/task_image/011
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/011. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/011/011.py
+* /xxx/ExeWorldBench/t1/task_image/011/011.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/t1/task_image/011/frame/011_000.png b/t1/task_image/011/frame/011_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..b119615fb4ab999bf27a67acd35dec20ae836c77
--- /dev/null
+++ b/t1/task_image/011/frame/011_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4f181b1b59fc7ac3f6f6b23e65b623fae04bdf9f9908c00c441787b804b0c239
+size 4669
diff --git a/t1/task_image/011/frame/011_001.png b/t1/task_image/011/frame/011_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..4881bb24d6ccbb670495f70d7ea4f51129f3ff01
--- /dev/null
+++ b/t1/task_image/011/frame/011_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:97b6507221fff10d172ce0ea4310359810b7cd224a2e57528fda68ef6ca55a8d
+size 5139
diff --git a/t1/task_image/011/frame/011_002.png b/t1/task_image/011/frame/011_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..a470b49bbe13baa955c04f39aff010ac73611e5b
--- /dev/null
+++ b/t1/task_image/011/frame/011_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5528e4a19149776786300782cb989827b4c70ba5de2c163d02ded9d3e1309ca8
+size 4824
diff --git a/t1/task_image/012/012.png b/t1/task_image/012/012.png
new file mode 100644
index 0000000000000000000000000000000000000000..66ac952db2ea1af459947741c20cd5ead307ce0a
--- /dev/null
+++ b/t1/task_image/012/012.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f3cb33cf707b7298a7c4d2bce8366e4eadf475f848b29cbc856743fa700338f6
+size 86296
diff --git a/t1/task_image/012/012.txt b/t1/task_image/012/012.txt
new file mode 100644
index 0000000000000000000000000000000000000000..03d84c7c483a3fc618a3af6818ceb4c1c6e0a962
--- /dev/null
+++ b/t1/task_image/012/012.txt
@@ -0,0 +1,82 @@
+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:
+012
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/012/012.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/012/frame/012_000.png, /xxx/ExeWorldBench/t1/task_image/012/frame/012_001.png, /xxx/ExeWorldBench/t1/task_image/012/frame/012_002.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/t1/task_image/012
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/012. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/012/012.py
+* /xxx/ExeWorldBench/t1/task_image/012/012.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/t1/task_image/012/frame/012_000.png b/t1/task_image/012/frame/012_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..c2e5d32fd8ca63fadac43459bd0840ccf8b58f0c
--- /dev/null
+++ b/t1/task_image/012/frame/012_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:495b1fac8fd0293a8e61c375e260126d8a86de720852107565448186319dc650
+size 10435
diff --git a/t1/task_image/012/frame/012_001.png b/t1/task_image/012/frame/012_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..6408cf11fcea5806c5e82d2f23548538f1872e25
--- /dev/null
+++ b/t1/task_image/012/frame/012_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5133479d6023f99e8a320419b21bf720c85bf50536d67ba83adb2f0990fd8273
+size 11595
diff --git a/t1/task_image/012/frame/012_002.png b/t1/task_image/012/frame/012_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..9a9dd3d85de9d24b4988aaebe97e50d88274b7bb
--- /dev/null
+++ b/t1/task_image/012/frame/012_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3046731cf4db2407d15b2d2cd7a022a2318da9486a251ee01c5926a2751cf130
+size 11539
diff --git a/t1/task_image/013/013.png b/t1/task_image/013/013.png
new file mode 100644
index 0000000000000000000000000000000000000000..4b11b6d1dba6ff3710ee2f2195acde9999fd37bc
--- /dev/null
+++ b/t1/task_image/013/013.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4857a01497c53065bc48777b5282df8efc8a5b5979fd15db746e99c4dcac2133
+size 71391
diff --git a/t1/task_image/013/013.txt b/t1/task_image/013/013.txt
new file mode 100644
index 0000000000000000000000000000000000000000..d28b24e46746a3bda3d363c6f39a9946c485d117
--- /dev/null
+++ b/t1/task_image/013/013.txt
@@ -0,0 +1,82 @@
+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:
+013
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/013/013.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/013/frame/013_000.png, /xxx/ExeWorldBench/t1/task_image/013/frame/013_001.png, /xxx/ExeWorldBench/t1/task_image/013/frame/013_002.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/t1/task_image/013
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/013. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/013/013.py
+* /xxx/ExeWorldBench/t1/task_image/013/013.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/t1/task_image/013/frame/013_000.png b/t1/task_image/013/frame/013_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..fafa3ea602632a4f7efa4cbcb90d553cc5b6247a
--- /dev/null
+++ b/t1/task_image/013/frame/013_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:84d7accc05a803afb54917394d912cbaa36f157338e5bc2a3d413ed92e8b299f
+size 10732
diff --git a/t1/task_image/013/frame/013_001.png b/t1/task_image/013/frame/013_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..f028d936987da255240b559fbec816f91069ce5a
--- /dev/null
+++ b/t1/task_image/013/frame/013_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dbccb3b31b47a8d71bf6aa86ffcc89ab3fdf522071f9196ab325b52cec6cc252
+size 10846
diff --git a/t1/task_image/013/frame/013_002.png b/t1/task_image/013/frame/013_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..c8e98e4256583ed5922963f715a7cc8c6ea8ad0f
--- /dev/null
+++ b/t1/task_image/013/frame/013_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:647a63e038e0d1d19bfe15e1716f9c73e1a257fd0dd789443d787fc7db19774e
+size 10963
diff --git a/t1/task_image/014/014.png b/t1/task_image/014/014.png
new file mode 100644
index 0000000000000000000000000000000000000000..6920ef2e6e3009d1a3deb2e82ef7b7976efd7bf8
--- /dev/null
+++ b/t1/task_image/014/014.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c911a75e2d63e6b85dc023915275bb5bed7b946ff316dfd1c5c61c388cfab05d
+size 11632
diff --git a/t1/task_image/014/014.txt b/t1/task_image/014/014.txt
new file mode 100644
index 0000000000000000000000000000000000000000..9352893c616651b6146865b54a9181f218246ab2
--- /dev/null
+++ b/t1/task_image/014/014.txt
@@ -0,0 +1,82 @@
+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:
+014
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/014/014.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/014/frame/014_000.png, /xxx/ExeWorldBench/t1/task_image/014/frame/014_001.png, /xxx/ExeWorldBench/t1/task_image/014/frame/014_002.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/t1/task_image/014
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/014. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/014/014.py
+* /xxx/ExeWorldBench/t1/task_image/014/014.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/t1/task_image/014/frame/014_000.png b/t1/task_image/014/frame/014_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..034c2dbd66ddde2e164558b75ad5899bd6201d13
--- /dev/null
+++ b/t1/task_image/014/frame/014_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9ff7f69d8180a1374a91a5111c5406a5d0bd70a64dc30422993705e95120a686
+size 3162
diff --git a/t1/task_image/014/frame/014_001.png b/t1/task_image/014/frame/014_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..997679250cb4dfe925be22b7cd627ec8c18c31f0
--- /dev/null
+++ b/t1/task_image/014/frame/014_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5553b9c1892436b32232c700649d638279455a8a940b682613a6eed83d3c63c0
+size 3169
diff --git a/t1/task_image/014/frame/014_002.png b/t1/task_image/014/frame/014_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..2a44b56c5cee7f783ddc3fdb4ddac32d50c3c91b
--- /dev/null
+++ b/t1/task_image/014/frame/014_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:41c8f2ab6d091088d2356e50e8c2c4448de083a51919459161383707627148d4
+size 3387
diff --git a/t1/task_image/015/015.png b/t1/task_image/015/015.png
new file mode 100644
index 0000000000000000000000000000000000000000..6d71c6bcbac36f77ef428f7de0f164c77de661a1
--- /dev/null
+++ b/t1/task_image/015/015.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aea8f421b7ba64fdf47ca8b170353b7dc0040d86d6cc82780b1bd0a584af4681
+size 18447
diff --git a/t1/task_image/015/015.txt b/t1/task_image/015/015.txt
new file mode 100644
index 0000000000000000000000000000000000000000..82295688617e359e21bc7e2da245e172c640ee40
--- /dev/null
+++ b/t1/task_image/015/015.txt
@@ -0,0 +1,82 @@
+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:
+015
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/015/015.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/015/frame/015_000.png, /xxx/ExeWorldBench/t1/task_image/015/frame/015_001.png, /xxx/ExeWorldBench/t1/task_image/015/frame/015_002.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/t1/task_image/015
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/015. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/015/015.py
+* /xxx/ExeWorldBench/t1/task_image/015/015.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/t1/task_image/015/frame/015_000.png b/t1/task_image/015/frame/015_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..89714448212e3c202c5a2f5f29631902871ccf55
--- /dev/null
+++ b/t1/task_image/015/frame/015_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:21ffd7bd51058488db369a448189d06a5d1ca8b20ea4dcb3df21764fd126f911
+size 3640
diff --git a/t1/task_image/015/frame/015_001.png b/t1/task_image/015/frame/015_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..8d95238b7872d3d6613d69cf89e89945ce2fd3a2
--- /dev/null
+++ b/t1/task_image/015/frame/015_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ee0d4a0944007f2886bf2c9a0ec6f3c6796c73dfe7fb9a93d293b79e9696a126
+size 3621
diff --git a/t1/task_image/015/frame/015_002.png b/t1/task_image/015/frame/015_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..e37111231efc433e51dcd089b0a19703ce456e9f
--- /dev/null
+++ b/t1/task_image/015/frame/015_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:50a93046856752b537231e0066909e489b15e7252597dc672d939b47b19cd9b0
+size 3758
diff --git a/t1/task_image/016/016.png b/t1/task_image/016/016.png
new file mode 100644
index 0000000000000000000000000000000000000000..ce1797f5f472e076492168f6e92f5dd0429eb4a1
--- /dev/null
+++ b/t1/task_image/016/016.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5e6d404da8fc63f18f645c2b09ccc5d48b165ff93b4c40df8e46ed45845d6eae
+size 96278
diff --git a/t1/task_image/016/016.txt b/t1/task_image/016/016.txt
new file mode 100644
index 0000000000000000000000000000000000000000..de3eff0bb9ec83682d9aa534a500cc423f68c3b9
--- /dev/null
+++ b/t1/task_image/016/016.txt
@@ -0,0 +1,82 @@
+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:
+016
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/016/016.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/016/frame/016_000.png, /xxx/ExeWorldBench/t1/task_image/016/frame/016_001.png, /xxx/ExeWorldBench/t1/task_image/016/frame/016_002.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/t1/task_image/016
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/016. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/016/016.py
+* /xxx/ExeWorldBench/t1/task_image/016/016.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/t1/task_image/016/frame/016_000.png b/t1/task_image/016/frame/016_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..e5e1b61d7941bb3c0f5e700a5724c92e1bb97369
--- /dev/null
+++ b/t1/task_image/016/frame/016_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2064747b845c10bab4c706d6c02e484466d5a1ee67a77e796e57b6e5d9a5c4de
+size 9569
diff --git a/t1/task_image/016/frame/016_001.png b/t1/task_image/016/frame/016_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..77f06efde073b8e2696972ba4af360050b24d053
--- /dev/null
+++ b/t1/task_image/016/frame/016_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b29b57a3f393f6fc72f89d9f6054c2616b80b6b49fa5bab3d08af1c880b3453e
+size 9444
diff --git a/t1/task_image/016/frame/016_002.png b/t1/task_image/016/frame/016_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..1ee291dbfa6ac90081f37a425ee5928dc013a272
--- /dev/null
+++ b/t1/task_image/016/frame/016_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7448bbc9e1a9772913e6fd549586c7439defc35067fe0e311f0a43ac2b08c456
+size 8720
diff --git a/t1/task_image/017/017.png b/t1/task_image/017/017.png
new file mode 100644
index 0000000000000000000000000000000000000000..61760c7c34a5c2f24f1136324b8d53aaf7ad6f0f
--- /dev/null
+++ b/t1/task_image/017/017.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:541869c258be1d29b3e6255f62c9a1083aba4b54386b4b48ba8d454dd1807314
+size 24667
diff --git a/t1/task_image/017/017.txt b/t1/task_image/017/017.txt
new file mode 100644
index 0000000000000000000000000000000000000000..6967848f8f0dc7df4e79554cc48e1d6dec30c86e
--- /dev/null
+++ b/t1/task_image/017/017.txt
@@ -0,0 +1,82 @@
+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:
+017
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/017/017.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/017/frame/017_000.png, /xxx/ExeWorldBench/t1/task_image/017/frame/017_001.png, /xxx/ExeWorldBench/t1/task_image/017/frame/017_002.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/t1/task_image/017
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/017. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/017/017.py
+* /xxx/ExeWorldBench/t1/task_image/017/017.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/t1/task_image/017/frame/017_000.png b/t1/task_image/017/frame/017_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..c7a5c2362c4a09bcf4e8c40ba93b1c1aaaf03a56
--- /dev/null
+++ b/t1/task_image/017/frame/017_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cbb6d78ae9b7b004528cae53ef19b74130f8c5cf194bc92441446423e8795880
+size 6319
diff --git a/t1/task_image/017/frame/017_001.png b/t1/task_image/017/frame/017_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..c7a5c2362c4a09bcf4e8c40ba93b1c1aaaf03a56
--- /dev/null
+++ b/t1/task_image/017/frame/017_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cbb6d78ae9b7b004528cae53ef19b74130f8c5cf194bc92441446423e8795880
+size 6319
diff --git a/t1/task_image/017/frame/017_002.png b/t1/task_image/017/frame/017_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..33daf10a1c2ab35c07820adcaffaed095224f6d5
--- /dev/null
+++ b/t1/task_image/017/frame/017_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2cdb0bfc0dc281fffd4128718d56d0af3e0815385671533830ff36bc8bbbc44d
+size 6265
diff --git a/t1/task_image/018/018.png b/t1/task_image/018/018.png
new file mode 100644
index 0000000000000000000000000000000000000000..eda90b272226e5f674e57aab63a20761d65f8f41
--- /dev/null
+++ b/t1/task_image/018/018.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:11063457a8afd64b370349a1318e75afd27332de49a3414923c7fec754873e50
+size 11184
diff --git a/t1/task_image/018/018.txt b/t1/task_image/018/018.txt
new file mode 100644
index 0000000000000000000000000000000000000000..c2fd4348b602765e0bf252d4ef19ed30c2572ced
--- /dev/null
+++ b/t1/task_image/018/018.txt
@@ -0,0 +1,82 @@
+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:
+018
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/018/018.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/018/frame/018_000.png, /xxx/ExeWorldBench/t1/task_image/018/frame/018_001.png, /xxx/ExeWorldBench/t1/task_image/018/frame/018_002.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/t1/task_image/018
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/018. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/018/018.py
+* /xxx/ExeWorldBench/t1/task_image/018/018.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/t1/task_image/018/frame/018_000.png b/t1/task_image/018/frame/018_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..f58790477b9d098c8109824b68f314e14df4eca7
--- /dev/null
+++ b/t1/task_image/018/frame/018_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:145d0f60a99151f32c3e39a04d9967211cd89545b5a6874b6b77cf8e5abe5c22
+size 4900
diff --git a/t1/task_image/018/frame/018_001.png b/t1/task_image/018/frame/018_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..ebc8aede9ef40cf7173238aaddf5304ee800fed4
--- /dev/null
+++ b/t1/task_image/018/frame/018_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aab9fa187878cf371fbfe55225997d218a705f56ae2c315e94972bfca6dcccf5
+size 5450
diff --git a/t1/task_image/018/frame/018_002.png b/t1/task_image/018/frame/018_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..6329578251fb91059b94d76974bea2252517c5d8
--- /dev/null
+++ b/t1/task_image/018/frame/018_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:402882708a0ea3c85333c743f1216411ca4f311d773f994de17f96ce1495efdc
+size 5725
diff --git a/t1/task_image/019/019.png b/t1/task_image/019/019.png
new file mode 100644
index 0000000000000000000000000000000000000000..56cf5e1faa8879529aec2ffdfbf413c006a1a8f4
--- /dev/null
+++ b/t1/task_image/019/019.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e2efd8d0538cfe960cf0547993fe9eac28bcb6d526e8eb15e4764c4d8b38bf0f
+size 34238
diff --git a/t1/task_image/019/019.txt b/t1/task_image/019/019.txt
new file mode 100644
index 0000000000000000000000000000000000000000..d23d1e785859da9e62593ad5e6b39ffb12e71e19
--- /dev/null
+++ b/t1/task_image/019/019.txt
@@ -0,0 +1,82 @@
+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:
+019
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/019/019.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/019/frame/019_000.png, /xxx/ExeWorldBench/t1/task_image/019/frame/019_001.png, /xxx/ExeWorldBench/t1/task_image/019/frame/019_002.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/t1/task_image/019
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/019. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/019/019.py
+* /xxx/ExeWorldBench/t1/task_image/019/019.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/t1/task_image/019/frame/019_000.png b/t1/task_image/019/frame/019_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..307d9c70674fa333dfeaffaa7b122104836f0f35
--- /dev/null
+++ b/t1/task_image/019/frame/019_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:51c42bb10eec0ca6ee3d86216a6beb46b52f08159fb63b08380e1683b2280bfd
+size 6686
diff --git a/t1/task_image/019/frame/019_001.png b/t1/task_image/019/frame/019_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..def75b2030bdc44ee1418f3845ad00730a8cd866
--- /dev/null
+++ b/t1/task_image/019/frame/019_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0212fd4abb75cc86941185558236a11734a008ae4a855d54d039d1022f5a9c2b
+size 5821
diff --git a/t1/task_image/019/frame/019_002.png b/t1/task_image/019/frame/019_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..f42e1f6a5115abf4b177ee43c2d92faa4b8a2685
--- /dev/null
+++ b/t1/task_image/019/frame/019_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a81c272cda22f50961b5860e7a01a0401deccec311b02473fd08ce0697a16547
+size 6212
diff --git a/t1/task_image/020/020.png b/t1/task_image/020/020.png
new file mode 100644
index 0000000000000000000000000000000000000000..06d72460470220ba8821afc31e36c6bceea99d98
--- /dev/null
+++ b/t1/task_image/020/020.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2424c2ea9fd6fbde01e218b8c0a512e095355f0a5a4989c2caabe20b1ebc817f
+size 51423
diff --git a/t1/task_image/020/020.txt b/t1/task_image/020/020.txt
new file mode 100644
index 0000000000000000000000000000000000000000..c569826f5d77ece8b9928ce8d112d7a349c9c679
--- /dev/null
+++ b/t1/task_image/020/020.txt
@@ -0,0 +1,82 @@
+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:
+020
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/020/020.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/020/frame/020_000.png, /xxx/ExeWorldBench/t1/task_image/020/frame/020_001.png, /xxx/ExeWorldBench/t1/task_image/020/frame/020_002.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/t1/task_image/020
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/020. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/020/020.py
+* /xxx/ExeWorldBench/t1/task_image/020/020.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/t1/task_image/020/frame/020_000.png b/t1/task_image/020/frame/020_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..7d4b8dba68e263ec428e911a137968c120b14b6d
--- /dev/null
+++ b/t1/task_image/020/frame/020_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9a6d0b95dd9d9d52a108e61e1e529c25bf0ddb61e705f7ce18ea25391450b1c4
+size 8416
diff --git a/t1/task_image/020/frame/020_001.png b/t1/task_image/020/frame/020_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..e67bd034245bfc8dbc412c52d1c04d893f569fe7
--- /dev/null
+++ b/t1/task_image/020/frame/020_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b429742ee22aae82ca3c485f390b6f8bc44dcb96380c0223bcbba087049484cf
+size 7688
diff --git a/t1/task_image/020/frame/020_002.png b/t1/task_image/020/frame/020_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..1188e0160617c9c68dd78af24c2669bdd685585c
--- /dev/null
+++ b/t1/task_image/020/frame/020_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:336a2dd7536716d0283f86439e22461cba099855f0ea1f3da4a919e1187d0472
+size 8050
diff --git a/t1/task_image/021/021.png b/t1/task_image/021/021.png
new file mode 100644
index 0000000000000000000000000000000000000000..8c17e6e11dd851f9896867091170e529b6a04ba2
--- /dev/null
+++ b/t1/task_image/021/021.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b25289ded3a8dfe1ba62ce9cbf66ce4f48e069d8b4dc245ba020089ce6073fba
+size 20428
diff --git a/t1/task_image/021/021.txt b/t1/task_image/021/021.txt
new file mode 100644
index 0000000000000000000000000000000000000000..e520189aef0003f67949ed8cbf8831bf63e477f9
--- /dev/null
+++ b/t1/task_image/021/021.txt
@@ -0,0 +1,82 @@
+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:
+021
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/021/021.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/021/frame/021_000.png, /xxx/ExeWorldBench/t1/task_image/021/frame/021_001.png, /xxx/ExeWorldBench/t1/task_image/021/frame/021_002.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/t1/task_image/021
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/021. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/021/021.py
+* /xxx/ExeWorldBench/t1/task_image/021/021.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/t1/task_image/021/frame/021_000.png b/t1/task_image/021/frame/021_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..27009c0773e2ba1dc515c5c0d2f4e9ba37dc5681
--- /dev/null
+++ b/t1/task_image/021/frame/021_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3241e2d5bd357b8dff47b44c5a5ebade869a9b2c4732678c71c8704dc5624896
+size 5752
diff --git a/t1/task_image/021/frame/021_001.png b/t1/task_image/021/frame/021_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..80b6ce2caacc93b688a6edebf562c035f3909b3a
--- /dev/null
+++ b/t1/task_image/021/frame/021_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3f81844a063cb7c60697fda82b73b9216e7eba30a42d7a2e6f92425509664c5e
+size 5369
diff --git a/t1/task_image/021/frame/021_002.png b/t1/task_image/021/frame/021_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..27009c0773e2ba1dc515c5c0d2f4e9ba37dc5681
--- /dev/null
+++ b/t1/task_image/021/frame/021_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3241e2d5bd357b8dff47b44c5a5ebade869a9b2c4732678c71c8704dc5624896
+size 5752
diff --git a/t1/task_image/022/022.png b/t1/task_image/022/022.png
new file mode 100644
index 0000000000000000000000000000000000000000..22dfe176258e3f31b7f01df928176207a12cc410
--- /dev/null
+++ b/t1/task_image/022/022.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:48a852c8aff3a9ee00127501f79b6344ca111ff766f77766feea27f7ae828ff2
+size 17821
diff --git a/t1/task_image/022/022.txt b/t1/task_image/022/022.txt
new file mode 100644
index 0000000000000000000000000000000000000000..e55b4a5246db70849426cfe17d83f3b3f7cf8a9e
--- /dev/null
+++ b/t1/task_image/022/022.txt
@@ -0,0 +1,82 @@
+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:
+022
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/022/022.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/022/frame/022_000.png, /xxx/ExeWorldBench/t1/task_image/022/frame/022_001.png, /xxx/ExeWorldBench/t1/task_image/022/frame/022_002.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/t1/task_image/022
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/022. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/022/022.py
+* /xxx/ExeWorldBench/t1/task_image/022/022.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/t1/task_image/022/frame/022_000.png b/t1/task_image/022/frame/022_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..03a5278830c70186f6ad7196550d6733c29f6190
--- /dev/null
+++ b/t1/task_image/022/frame/022_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ac9248704ec312d26d0bcb6c9f28a1d85208779dfe0334482afdfeac98bc737d
+size 5016
diff --git a/t1/task_image/022/frame/022_001.png b/t1/task_image/022/frame/022_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..47e1c5251c58061e83bd3bfb960675290aaeac12
--- /dev/null
+++ b/t1/task_image/022/frame/022_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:83dfedae911a43c870c92007d8331a67ac8ca087f0a4b1f9e1a4491b7b857bec
+size 5385
diff --git a/t1/task_image/022/frame/022_002.png b/t1/task_image/022/frame/022_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..d329e5a0b89b865b55c25b53a35a07b232666c14
--- /dev/null
+++ b/t1/task_image/022/frame/022_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f3d174f7915ee17392d866006b9fefc6633aec12fe5555028248b5a47388ddf7
+size 4920
diff --git a/t1/task_image/023/023.png b/t1/task_image/023/023.png
new file mode 100644
index 0000000000000000000000000000000000000000..3f5c026a652ab28adcdf39693ecf84134f0a81f2
--- /dev/null
+++ b/t1/task_image/023/023.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:59ff70d4426f772eed3e467209f5b2a7d1a00a69e5e4e3b0551a325c03eec9a7
+size 34704
diff --git a/t1/task_image/023/023.txt b/t1/task_image/023/023.txt
new file mode 100644
index 0000000000000000000000000000000000000000..181c90949aff03475798e3190ad47e353d4b39d8
--- /dev/null
+++ b/t1/task_image/023/023.txt
@@ -0,0 +1,82 @@
+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:
+023
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/023/023.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/023/frame/023_000.png, /xxx/ExeWorldBench/t1/task_image/023/frame/023_001.png, /xxx/ExeWorldBench/t1/task_image/023/frame/023_002.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/t1/task_image/023
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/023. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/023/023.py
+* /xxx/ExeWorldBench/t1/task_image/023/023.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/t1/task_image/023/frame/023_000.png b/t1/task_image/023/frame/023_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..fce48cca10149936c449f2ef097c25e86f686adc
--- /dev/null
+++ b/t1/task_image/023/frame/023_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:31b87ba6f9aefbcbef1c82606b61e052b619f2207493274eb6e73283a422ea8f
+size 6583
diff --git a/t1/task_image/023/frame/023_001.png b/t1/task_image/023/frame/023_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..8db5b27f8e8caf403eb43481892dc1366d5f481c
--- /dev/null
+++ b/t1/task_image/023/frame/023_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:62523c8f626df2af74747c7f8cc7cafefbb6fc5a67db3cb317c85441902e881a
+size 6582
diff --git a/t1/task_image/023/frame/023_002.png b/t1/task_image/023/frame/023_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..360ab52d29b8d317d1f4fd72ffdd49dc876bc772
--- /dev/null
+++ b/t1/task_image/023/frame/023_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:632f2fe99a7de8955c6d41f8428bb83e6e4c2becea5286a7ad78159eddb07a9a
+size 6587
diff --git a/t1/task_image/024/024.png b/t1/task_image/024/024.png
new file mode 100644
index 0000000000000000000000000000000000000000..4d48a99fe3cd7baa7bf993b01007a3676eb4c66e
--- /dev/null
+++ b/t1/task_image/024/024.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6c004ebb4accdfe66de32f5310330b2b5636caf6e53d46db6af73e7e346db162
+size 18666
diff --git a/t1/task_image/024/024.txt b/t1/task_image/024/024.txt
new file mode 100644
index 0000000000000000000000000000000000000000..9b79a8272cc24bd0569c2b29b63788900ee41985
--- /dev/null
+++ b/t1/task_image/024/024.txt
@@ -0,0 +1,82 @@
+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:
+024
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/024/024.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/024/frame/024_000.png, /xxx/ExeWorldBench/t1/task_image/024/frame/024_001.png, /xxx/ExeWorldBench/t1/task_image/024/frame/024_002.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/t1/task_image/024
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/024. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/024/024.py
+* /xxx/ExeWorldBench/t1/task_image/024/024.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/t1/task_image/024/frame/024_000.png b/t1/task_image/024/frame/024_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..0abc358fe97e49da7bdcc94e74ed1d5fe5942375
--- /dev/null
+++ b/t1/task_image/024/frame/024_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:df3e0efae98784f7404da9203f4aba6800db39ae6abadb3543320799f5c4c588
+size 4983
diff --git a/t1/task_image/024/frame/024_001.png b/t1/task_image/024/frame/024_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..505b45e2f6940b803e5da1fde05219e8fabd999d
--- /dev/null
+++ b/t1/task_image/024/frame/024_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:317759769b33703050d7cd51c38343b58d4e48ad79930069d7227bb1afb259c0
+size 5132
diff --git a/t1/task_image/024/frame/024_002.png b/t1/task_image/024/frame/024_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..a262b87c2b23e6d28f5f9eeff9b83046bcdfac2a
--- /dev/null
+++ b/t1/task_image/024/frame/024_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3b8c340cfe4af7036ef7f1d3009910c227ca09e2f7e477fe28f10970c38a219d
+size 5121
diff --git a/t1/task_image/025/025.png b/t1/task_image/025/025.png
new file mode 100644
index 0000000000000000000000000000000000000000..9ec43384817c90c331fbbab5fbf5bed68f7ee1c2
--- /dev/null
+++ b/t1/task_image/025/025.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f6b97a7579e53d3d01e9de10bd712e81fd0cb1e19bf18e9e77339145edf73866
+size 117640
diff --git a/t1/task_image/025/025.txt b/t1/task_image/025/025.txt
new file mode 100644
index 0000000000000000000000000000000000000000..c0d765611653345e952b0ceb43798da25933e15e
--- /dev/null
+++ b/t1/task_image/025/025.txt
@@ -0,0 +1,82 @@
+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:
+025
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/025/025.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/025/frame/025_000.png, /xxx/ExeWorldBench/t1/task_image/025/frame/025_001.png, /xxx/ExeWorldBench/t1/task_image/025/frame/025_002.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/t1/task_image/025
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/025. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/025/025.py
+* /xxx/ExeWorldBench/t1/task_image/025/025.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/t1/task_image/025/frame/025_000.png b/t1/task_image/025/frame/025_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..c9933e09fe1054863a890966e30eb3069a4f4442
--- /dev/null
+++ b/t1/task_image/025/frame/025_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d179a5ecf0ee15bfc0926c59cc15fd28b3e9d04e7a3411965519bb1dd9333615
+size 15549
diff --git a/t1/task_image/025/frame/025_001.png b/t1/task_image/025/frame/025_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..3755031f020948b32d8fa7ae7f4f5f9a7d06b279
--- /dev/null
+++ b/t1/task_image/025/frame/025_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:70645d4d8e90ffee197dadec9445f323a3e4f6e01066ec8be52ae8aaa9464a1a
+size 14411
diff --git a/t1/task_image/025/frame/025_002.png b/t1/task_image/025/frame/025_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..5f53eb774c812ed44a2e6ff2b680ce92f4d508f3
--- /dev/null
+++ b/t1/task_image/025/frame/025_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aa1c3df9d4eaec0427b346eee173f428f816383189119283a1c3a03fbf2f3095
+size 13726
diff --git a/t1/task_image/026/026.png b/t1/task_image/026/026.png
new file mode 100644
index 0000000000000000000000000000000000000000..57d6583b2d01a14cc638aa4a0a9f87fc4f537fc5
--- /dev/null
+++ b/t1/task_image/026/026.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:88fae427ae1487f0af42eab914e4ebd69bc9779c8acd812737b3d3c23a23d82c
+size 159802
diff --git a/t1/task_image/026/026.txt b/t1/task_image/026/026.txt
new file mode 100644
index 0000000000000000000000000000000000000000..d2b920f14de250dbaef3347b40b411e6c5109eb8
--- /dev/null
+++ b/t1/task_image/026/026.txt
@@ -0,0 +1,82 @@
+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:
+026
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/026/026.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/026/frame/026_000.png, /xxx/ExeWorldBench/t1/task_image/026/frame/026_001.png, /xxx/ExeWorldBench/t1/task_image/026/frame/026_002.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/t1/task_image/026
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/026. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/026/026.py
+* /xxx/ExeWorldBench/t1/task_image/026/026.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/t1/task_image/026/frame/026_000.png b/t1/task_image/026/frame/026_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..c205b95dc114a358c798c2987f40d28ad3809ee2
--- /dev/null
+++ b/t1/task_image/026/frame/026_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ced94720b1a87d2fe15870593bebffecfd5bbc6834a762cc5891dc5840798b04
+size 18886
diff --git a/t1/task_image/026/frame/026_001.png b/t1/task_image/026/frame/026_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..f14ae3ef96c3bf0c5a873a232dce9d4ab66ce921
--- /dev/null
+++ b/t1/task_image/026/frame/026_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:18e71b1189326fc102fda61ea6b7858e6d8df575c5fef84e9b69dab0e0a29c3d
+size 18996
diff --git a/t1/task_image/026/frame/026_002.png b/t1/task_image/026/frame/026_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..9c92fd4253af6e5a0532d5a91606e056aae8eaa8
--- /dev/null
+++ b/t1/task_image/026/frame/026_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:95f36c8bc5b6922819dd09dced7289f077e023827096765e1b4da32aeb00f21b
+size 18779
diff --git a/t1/task_image/027/027.png b/t1/task_image/027/027.png
new file mode 100644
index 0000000000000000000000000000000000000000..3f96efba5ce37c91837d72abf598db97867c34e6
--- /dev/null
+++ b/t1/task_image/027/027.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d8592d4b6150a9b1eaaca0b81fbfe09a74e652df6bedaf0a49bb91f68d827f8d
+size 34843
diff --git a/t1/task_image/027/027.txt b/t1/task_image/027/027.txt
new file mode 100644
index 0000000000000000000000000000000000000000..fc7aecc3434c7352fd45e0d7aa5b1bb9924be1c1
--- /dev/null
+++ b/t1/task_image/027/027.txt
@@ -0,0 +1,82 @@
+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:
+027
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/027/027.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/027/frame/027_000.png, /xxx/ExeWorldBench/t1/task_image/027/frame/027_001.png, /xxx/ExeWorldBench/t1/task_image/027/frame/027_002.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/t1/task_image/027
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/027. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/027/027.py
+* /xxx/ExeWorldBench/t1/task_image/027/027.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/t1/task_image/027/frame/027_000.png b/t1/task_image/027/frame/027_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..cdb4cd95f5912f9889a5dbcdd5f67af321ac2329
--- /dev/null
+++ b/t1/task_image/027/frame/027_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:48d5b9ce70c390b931b0f7aa187cdea128063dc750a96c24f4392a6de40a37b9
+size 5884
diff --git a/t1/task_image/027/frame/027_001.png b/t1/task_image/027/frame/027_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..c1fa3bb1bb9886df8cd605130ed839c66694c0c1
--- /dev/null
+++ b/t1/task_image/027/frame/027_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fbf27e5f6d1059ef64e258d953698822a000515b6c9a43bf1ef34187c15979f7
+size 5846
diff --git a/t1/task_image/027/frame/027_002.png b/t1/task_image/027/frame/027_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..9ec67bf6a73166719dd661c2b3aba0fe5f77ab7b
--- /dev/null
+++ b/t1/task_image/027/frame/027_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6d80f4280b22e762d088bdbcae18a5aec482c8693ac680e0570f2762e0eb5068
+size 5881
diff --git a/t1/task_image/028/028.png b/t1/task_image/028/028.png
new file mode 100644
index 0000000000000000000000000000000000000000..4edcb8de032504e2484409eae0df5e731ff29b3d
--- /dev/null
+++ b/t1/task_image/028/028.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:da691d6833a5107502247944f5770ed8a74c8424057ffe6aed83183c7312b07c
+size 23430
diff --git a/t1/task_image/028/028.txt b/t1/task_image/028/028.txt
new file mode 100644
index 0000000000000000000000000000000000000000..9e24793b191ff4228f53e5b38550a87de79ade9c
--- /dev/null
+++ b/t1/task_image/028/028.txt
@@ -0,0 +1,82 @@
+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:
+028
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/028/028.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/028/frame/028_000.png, /xxx/ExeWorldBench/t1/task_image/028/frame/028_001.png, /xxx/ExeWorldBench/t1/task_image/028/frame/028_002.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/t1/task_image/028
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/028. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/028/028.py
+* /xxx/ExeWorldBench/t1/task_image/028/028.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/t1/task_image/028/frame/028_000.png b/t1/task_image/028/frame/028_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..363c98031105e8144908876ae7d4d097fb6fd3da
--- /dev/null
+++ b/t1/task_image/028/frame/028_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:75a83bd65328e7d5de6df82b3eb10262792b0fd7091cbe94479342154bbfc2bb
+size 5427
diff --git a/t1/task_image/028/frame/028_001.png b/t1/task_image/028/frame/028_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..1e1f1186432aa783f938fec3d885a97b45f7c2c3
--- /dev/null
+++ b/t1/task_image/028/frame/028_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8571926c3dc506f37cc1a14c3b6f23ab1cebc1993d856f395ffe3138f7a793b8
+size 5401
diff --git a/t1/task_image/028/frame/028_002.png b/t1/task_image/028/frame/028_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..4171236f2448771a0e3b9e34ad2254e7b74ee712
--- /dev/null
+++ b/t1/task_image/028/frame/028_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a0ef6389127a5425659b5b3e7eecfa93937f23c2eaa8829f5e0dba380870a05c
+size 5479
diff --git a/t1/task_image/029/029.png b/t1/task_image/029/029.png
new file mode 100644
index 0000000000000000000000000000000000000000..f9d85c1419cf4320f3b7d8c6a8ac95211b6a6420
--- /dev/null
+++ b/t1/task_image/029/029.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bfe1e0b727d86a1381a6936a98cf83c000ecdf4eb26aa87781c69978cc8c5ff8
+size 47496
diff --git a/t1/task_image/029/029.txt b/t1/task_image/029/029.txt
new file mode 100644
index 0000000000000000000000000000000000000000..2f23cb18e58da73cac84628a69f95b70fa8f3c6e
--- /dev/null
+++ b/t1/task_image/029/029.txt
@@ -0,0 +1,82 @@
+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:
+029
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/029/029.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/029/frame/029_000.png, /xxx/ExeWorldBench/t1/task_image/029/frame/029_001.png, /xxx/ExeWorldBench/t1/task_image/029/frame/029_002.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/t1/task_image/029
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/029. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/029/029.py
+* /xxx/ExeWorldBench/t1/task_image/029/029.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/t1/task_image/029/frame/029_000.png b/t1/task_image/029/frame/029_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..81f7ccadcc23b57843047c3cf6713103c0561352
--- /dev/null
+++ b/t1/task_image/029/frame/029_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:15ceeae92598826e300676559db3a6daa41ccbe8ea1b5cc4440c2a5bb90d4684
+size 9301
diff --git a/t1/task_image/029/frame/029_001.png b/t1/task_image/029/frame/029_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..f3828cc9375ff6c24e30b3218f358e7b12598137
--- /dev/null
+++ b/t1/task_image/029/frame/029_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ff3238f79cb3d0a3bccbefb4655e44dd66e1a167599d6844e25fbf725f96e3ac
+size 9875
diff --git a/t1/task_image/029/frame/029_002.png b/t1/task_image/029/frame/029_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..15695d35112e471b054b8bba9daf5824a056fd5f
--- /dev/null
+++ b/t1/task_image/029/frame/029_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a90a1077c3b4147cb90064a36cc0206fd18277e98820047d5e225b42274e8c10
+size 9361
diff --git a/t1/task_image/030/030.png b/t1/task_image/030/030.png
new file mode 100644
index 0000000000000000000000000000000000000000..d411fe2476c58d0b8981a112c2b6bff451f6a4e2
--- /dev/null
+++ b/t1/task_image/030/030.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d45875272e365e9992f8ec5f378b1482018e92d72b6e5f61cd83d9d46980c23a
+size 15406
diff --git a/t1/task_image/030/030.txt b/t1/task_image/030/030.txt
new file mode 100644
index 0000000000000000000000000000000000000000..d7d249ed43b8dd5d6ab23d27b76ad6b298079b4c
--- /dev/null
+++ b/t1/task_image/030/030.txt
@@ -0,0 +1,82 @@
+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:
+030
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/030/030.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/030/frame/030_000.png, /xxx/ExeWorldBench/t1/task_image/030/frame/030_001.png, /xxx/ExeWorldBench/t1/task_image/030/frame/030_002.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/t1/task_image/030
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/030. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/030/030.py
+* /xxx/ExeWorldBench/t1/task_image/030/030.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/t1/task_image/030/frame/030_000.png b/t1/task_image/030/frame/030_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..b9f39329cef4a4eb199a47f1da9f4a00cba232de
--- /dev/null
+++ b/t1/task_image/030/frame/030_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:adf43732b7bb8fbfdd6ce230f813c1b86acebffdb1a6c33cd4302630f1e54991
+size 5061
diff --git a/t1/task_image/030/frame/030_001.png b/t1/task_image/030/frame/030_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..960eb2a38d9dcfd9a819b3c6d7ba1e9b4535470d
--- /dev/null
+++ b/t1/task_image/030/frame/030_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ba6e2ae0ae29118cb9879ff994d903e048eb32864ca876a6cb9ea3b505a7dbb9
+size 5072
diff --git a/t1/task_image/030/frame/030_002.png b/t1/task_image/030/frame/030_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..960eb2a38d9dcfd9a819b3c6d7ba1e9b4535470d
--- /dev/null
+++ b/t1/task_image/030/frame/030_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ba6e2ae0ae29118cb9879ff994d903e048eb32864ca876a6cb9ea3b505a7dbb9
+size 5072
diff --git a/t1/task_image/031/031.png b/t1/task_image/031/031.png
new file mode 100644
index 0000000000000000000000000000000000000000..117d995d87165460701e435fb3cb9e673242354a
--- /dev/null
+++ b/t1/task_image/031/031.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9237ca3a1b3212fedb058c842e7c5f414b5fe81b4c42cdfdd2df791f3dc3182b
+size 40746
diff --git a/t1/task_image/031/031.txt b/t1/task_image/031/031.txt
new file mode 100644
index 0000000000000000000000000000000000000000..4fe214979ac5dd8215eea2e9de516f02a3b05af0
--- /dev/null
+++ b/t1/task_image/031/031.txt
@@ -0,0 +1,82 @@
+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:
+031
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/031/031.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/031/frame/031_000.png, /xxx/ExeWorldBench/t1/task_image/031/frame/031_001.png, /xxx/ExeWorldBench/t1/task_image/031/frame/031_002.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/t1/task_image/031
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/031. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/031/031.py
+* /xxx/ExeWorldBench/t1/task_image/031/031.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/t1/task_image/031/frame/031_000.png b/t1/task_image/031/frame/031_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..97d8f2922dca0a18c6fec6328897e90615548f45
--- /dev/null
+++ b/t1/task_image/031/frame/031_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:98ddb899700bd54c5238a368b058e2361717020d677df8a3ffa5680311fcd414
+size 7488
diff --git a/t1/task_image/031/frame/031_001.png b/t1/task_image/031/frame/031_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..174ac4e5f4acc6d174c96a2360d43a772d5e2084
--- /dev/null
+++ b/t1/task_image/031/frame/031_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5453a323feb02cd8739f0b84f0a8264cfdafd490016d508901457bde9377bdb2
+size 6645
diff --git a/t1/task_image/031/frame/031_002.png b/t1/task_image/031/frame/031_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..2f14bf2dfa067d7fe085ad2bf75e955e6ec813be
--- /dev/null
+++ b/t1/task_image/031/frame/031_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6bf120069cdfedaf912874bfedc41835d7d789598915220d31882addaaec8ceb
+size 8005
diff --git a/t1/task_image/032/032.png b/t1/task_image/032/032.png
new file mode 100644
index 0000000000000000000000000000000000000000..d62c1399116da8536e9bf9ba26af300f4c424189
--- /dev/null
+++ b/t1/task_image/032/032.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:55f93769887f3b31bde974afcce8b3d121ecb2d270d09bb0b36b72118ddf6c5f
+size 48456
diff --git a/t1/task_image/032/032.txt b/t1/task_image/032/032.txt
new file mode 100644
index 0000000000000000000000000000000000000000..c39e033fb49e40ddba28ea25aa83f3eb90c0bba4
--- /dev/null
+++ b/t1/task_image/032/032.txt
@@ -0,0 +1,82 @@
+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:
+032
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/032/032.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/032/frame/032_000.png, /xxx/ExeWorldBench/t1/task_image/032/frame/032_001.png, /xxx/ExeWorldBench/t1/task_image/032/frame/032_002.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/t1/task_image/032
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/032. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/032/032.py
+* /xxx/ExeWorldBench/t1/task_image/032/032.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/t1/task_image/032/frame/032_000.png b/t1/task_image/032/frame/032_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..49abe4a1b1310ae085e9ebd5a43980a77065cfec
--- /dev/null
+++ b/t1/task_image/032/frame/032_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7564176ff6d7e28e2cf275aab280aa6d62f007f2fa18eb274341ecbaf8bde952
+size 12521
diff --git a/t1/task_image/032/frame/032_001.png b/t1/task_image/032/frame/032_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..ce0855080a631645c771343707a3b7b809d3e80b
--- /dev/null
+++ b/t1/task_image/032/frame/032_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:15aff81fbde6fbb881b389bb04eb2418d8ba2ed58a4468c809902e52d340e882
+size 12901
diff --git a/t1/task_image/032/frame/032_002.png b/t1/task_image/032/frame/032_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..f3dd8b8558589080c210d6b00723105c3c01b31a
--- /dev/null
+++ b/t1/task_image/032/frame/032_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aeb3a9c826cdbdb4583617285521bb435fc082a2a1197f9121659ace687a7d3d
+size 13218
diff --git a/t1/task_image/033/033.png b/t1/task_image/033/033.png
new file mode 100644
index 0000000000000000000000000000000000000000..d6456ff3a9998d4c500e5b7aa2e789b8096ee551
--- /dev/null
+++ b/t1/task_image/033/033.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9f48b718c00c88fb71137b08b78f5ccc9a739f4b09f72677d266c536ddeca899
+size 46919
diff --git a/t1/task_image/033/033.txt b/t1/task_image/033/033.txt
new file mode 100644
index 0000000000000000000000000000000000000000..553d98b94439a2e5360b6f45ef53af9633184406
--- /dev/null
+++ b/t1/task_image/033/033.txt
@@ -0,0 +1,82 @@
+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:
+033
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/033/033.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/033/frame/033_000.png, /xxx/ExeWorldBench/t1/task_image/033/frame/033_001.png, /xxx/ExeWorldBench/t1/task_image/033/frame/033_002.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/t1/task_image/033
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/033. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/033/033.py
+* /xxx/ExeWorldBench/t1/task_image/033/033.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/t1/task_image/033/frame/033_000.png b/t1/task_image/033/frame/033_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..93d082dab2afffe1ce6f92e7718a87367dcd8bf7
--- /dev/null
+++ b/t1/task_image/033/frame/033_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4944bba402b0dfd4c353ada21c1aa7943bdb6fffbef5288266f72d50f8f92472
+size 7886
diff --git a/t1/task_image/033/frame/033_001.png b/t1/task_image/033/frame/033_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..b48a74ce10ec4a1ae59b20e4ace6348a394e981b
--- /dev/null
+++ b/t1/task_image/033/frame/033_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c3ce1d434eae8c83bea8c4bdbfa59c5590b70af5a76cecccbbc2282a4b6e86fe
+size 7990
diff --git a/t1/task_image/033/frame/033_002.png b/t1/task_image/033/frame/033_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..48e272362c0bb0076712e75586f3bf64bbfd7073
--- /dev/null
+++ b/t1/task_image/033/frame/033_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:26e40ccb251912e6861d57c5470260b982609e0d00ddc60fd34914964af9ee57
+size 8219
diff --git a/t1/task_image/034/034.png b/t1/task_image/034/034.png
new file mode 100644
index 0000000000000000000000000000000000000000..f3186abce50aa81b6a1f95c357e2bd29d086ad90
--- /dev/null
+++ b/t1/task_image/034/034.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ba0d4b2d47d8e90d3482ef3fe2a61f10a0f1644aaa70f15df56db9cfbc6d24c4
+size 37638
diff --git a/t1/task_image/034/034.txt b/t1/task_image/034/034.txt
new file mode 100644
index 0000000000000000000000000000000000000000..4ae7656793660d546d7e2305f230e44cd208d14f
--- /dev/null
+++ b/t1/task_image/034/034.txt
@@ -0,0 +1,82 @@
+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:
+034
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/034/034.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/034/frame/034_000.png, /xxx/ExeWorldBench/t1/task_image/034/frame/034_001.png, /xxx/ExeWorldBench/t1/task_image/034/frame/034_002.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/t1/task_image/034
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/034. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/034/034.py
+* /xxx/ExeWorldBench/t1/task_image/034/034.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/t1/task_image/034/frame/034_000.png b/t1/task_image/034/frame/034_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..f62efabdbfb1c7b2aba9f831cd7839ee69dc2c21
--- /dev/null
+++ b/t1/task_image/034/frame/034_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7f0f78252cd2465fb56f666e3b6ebe26976f8cfd0950f7ad4ea36a26db567091
+size 6529
diff --git a/t1/task_image/034/frame/034_001.png b/t1/task_image/034/frame/034_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..dbfb329e473e0f09b0a3cbcc814ac43d124ce6d2
--- /dev/null
+++ b/t1/task_image/034/frame/034_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b09899ac527000a524e6de42a3dd3989355fe3dccb37fea7c6723754c46ca86c
+size 6711
diff --git a/t1/task_image/034/frame/034_002.png b/t1/task_image/034/frame/034_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..d5d3c6eecafdf47f914514296bb99a486b32c376
--- /dev/null
+++ b/t1/task_image/034/frame/034_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:83c8cf7e99d900ad894a34ed256097fc40a47450134278df2f50a5615f4910eb
+size 6561
diff --git a/t1/task_image/035/035.png b/t1/task_image/035/035.png
new file mode 100644
index 0000000000000000000000000000000000000000..386ad71a7271fb35cbe8cd4f1d2bb419311891dd
--- /dev/null
+++ b/t1/task_image/035/035.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3fc37ac7f4c8f1adbe5484bffdb94d68e4a33c35038fb975047d30ebdb153301
+size 52696
diff --git a/t1/task_image/035/035.txt b/t1/task_image/035/035.txt
new file mode 100644
index 0000000000000000000000000000000000000000..b830feefdb0ebd4efecbad98de6cb914d9b99a9b
--- /dev/null
+++ b/t1/task_image/035/035.txt
@@ -0,0 +1,82 @@
+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:
+035
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/035/035.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/035/frame/035_000.png, /xxx/ExeWorldBench/t1/task_image/035/frame/035_001.png, /xxx/ExeWorldBench/t1/task_image/035/frame/035_002.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/t1/task_image/035
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/035. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/035/035.py
+* /xxx/ExeWorldBench/t1/task_image/035/035.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/t1/task_image/035/frame/035_000.png b/t1/task_image/035/frame/035_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..dc9e0543511ab72f28d028ed869373c64a46541d
--- /dev/null
+++ b/t1/task_image/035/frame/035_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9ff72687f41d9bb8a1ece5af919749f6f1a81e200cd7013fb54acec96cb2784e
+size 9019
diff --git a/t1/task_image/035/frame/035_001.png b/t1/task_image/035/frame/035_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..c6f4ba99c7dfb73073eaa2379fb27ad84fbc3c76
--- /dev/null
+++ b/t1/task_image/035/frame/035_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c4c0b49beeeb90ce50b5fe5d2fee7f9ca308d4ff4d1a28d1b18edb475cf9d5cb
+size 8534
diff --git a/t1/task_image/035/frame/035_002.png b/t1/task_image/035/frame/035_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..60d603a176aa3b1037ae761a372a5e8f940acb20
--- /dev/null
+++ b/t1/task_image/035/frame/035_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b0d6b00628c3a39c1af9a17df3b8d82c23e1d5083df62dae89ad245904fb0b2b
+size 8934
diff --git a/t1/task_image/036/036.png b/t1/task_image/036/036.png
new file mode 100644
index 0000000000000000000000000000000000000000..c394fc8d002cb2e85696f570580fea9bc287c9d6
--- /dev/null
+++ b/t1/task_image/036/036.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0ff74860787e618fbcb7ae70590ef99431606289a469412d48cce722e81362b8
+size 44233
diff --git a/t1/task_image/036/036.txt b/t1/task_image/036/036.txt
new file mode 100644
index 0000000000000000000000000000000000000000..1565468e4061394ebaad6fff31124bd933d7ef83
--- /dev/null
+++ b/t1/task_image/036/036.txt
@@ -0,0 +1,82 @@
+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:
+036
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/036/036.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/036/frame/036_000.png, /xxx/ExeWorldBench/t1/task_image/036/frame/036_001.png, /xxx/ExeWorldBench/t1/task_image/036/frame/036_002.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/t1/task_image/036
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/036. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/036/036.py
+* /xxx/ExeWorldBench/t1/task_image/036/036.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/t1/task_image/036/frame/036_000.png b/t1/task_image/036/frame/036_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..545b042c302e4a1c5ee26583c0185e45b8f2ec68
--- /dev/null
+++ b/t1/task_image/036/frame/036_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6434484827a4f67bcd5f46a4d4f3bd6640799eeb72e74b79bfc0657b776af5d4
+size 7801
diff --git a/t1/task_image/036/frame/036_001.png b/t1/task_image/036/frame/036_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..c934d4b5d00db56677ea686bdfd404a26860d938
--- /dev/null
+++ b/t1/task_image/036/frame/036_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2425b810d0fdaf189d3a1829f4f4d14f4d39b966ddfa179b9be34bcbdecf3b11
+size 7789
diff --git a/t1/task_image/036/frame/036_002.png b/t1/task_image/036/frame/036_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..56d2724de02b7bf354e8109c4b0dbd2aa06fb693
--- /dev/null
+++ b/t1/task_image/036/frame/036_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9100c174d7d6433575f6a4155d4488192ee63292a9262d063f151818b00a90c6
+size 7784
diff --git a/t1/task_image/037/037.png b/t1/task_image/037/037.png
new file mode 100644
index 0000000000000000000000000000000000000000..ef73c3950de8a50eac83e7e8b85812281bd5f4e0
--- /dev/null
+++ b/t1/task_image/037/037.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a72b13e5c1821d3c4b008668d93b74804aa96df6b39fac40cd21d6b515069ad2
+size 18118
diff --git a/t1/task_image/037/037.txt b/t1/task_image/037/037.txt
new file mode 100644
index 0000000000000000000000000000000000000000..d1e6a7dc7cffbe4d9c13e164eca2b0369e363c6b
--- /dev/null
+++ b/t1/task_image/037/037.txt
@@ -0,0 +1,82 @@
+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:
+037
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/037/037.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/037/frame/037_000.png, /xxx/ExeWorldBench/t1/task_image/037/frame/037_001.png, /xxx/ExeWorldBench/t1/task_image/037/frame/037_002.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/t1/task_image/037
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/037. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/037/037.py
+* /xxx/ExeWorldBench/t1/task_image/037/037.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/t1/task_image/037/frame/037_000.png b/t1/task_image/037/frame/037_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..f58790477b9d098c8109824b68f314e14df4eca7
--- /dev/null
+++ b/t1/task_image/037/frame/037_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:145d0f60a99151f32c3e39a04d9967211cd89545b5a6874b6b77cf8e5abe5c22
+size 4900
diff --git a/t1/task_image/037/frame/037_001.png b/t1/task_image/037/frame/037_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..ebc8aede9ef40cf7173238aaddf5304ee800fed4
--- /dev/null
+++ b/t1/task_image/037/frame/037_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aab9fa187878cf371fbfe55225997d218a705f56ae2c315e94972bfca6dcccf5
+size 5450
diff --git a/t1/task_image/037/frame/037_002.png b/t1/task_image/037/frame/037_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..6329578251fb91059b94d76974bea2252517c5d8
--- /dev/null
+++ b/t1/task_image/037/frame/037_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:402882708a0ea3c85333c743f1216411ca4f311d773f994de17f96ce1495efdc
+size 5725
diff --git a/t1/task_image/038/038.png b/t1/task_image/038/038.png
new file mode 100644
index 0000000000000000000000000000000000000000..b0d4a2f435b5acba6a2a28f5316ba8b51b46329f
--- /dev/null
+++ b/t1/task_image/038/038.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5801a738b68d7f755213b6b86adc6f3f9e7d8395739df0426dd7e1849c30b012
+size 44761
diff --git a/t1/task_image/038/038.txt b/t1/task_image/038/038.txt
new file mode 100644
index 0000000000000000000000000000000000000000..17e32725b3a4238871e7936db37b2265bfe73d20
--- /dev/null
+++ b/t1/task_image/038/038.txt
@@ -0,0 +1,82 @@
+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:
+038
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/038/038.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/038/frame/038_000.png, /xxx/ExeWorldBench/t1/task_image/038/frame/038_001.png, /xxx/ExeWorldBench/t1/task_image/038/frame/038_002.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/t1/task_image/038
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/038. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/038/038.py
+* /xxx/ExeWorldBench/t1/task_image/038/038.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/t1/task_image/038/frame/038_000.png b/t1/task_image/038/frame/038_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..8a9d9c1756de887eedb07f680625f58c3ea419ba
--- /dev/null
+++ b/t1/task_image/038/frame/038_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:63f3136127fb9c09a561ed07a3b5f0b0da26b83c6a941bf4cd1fbecb474a7bae
+size 6515
diff --git a/t1/task_image/038/frame/038_001.png b/t1/task_image/038/frame/038_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..4e0c9ff78c93aced62a3cde5839a47c873a22004
--- /dev/null
+++ b/t1/task_image/038/frame/038_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:83734ae7dfc8f754a21872ee46b26a8c7c64003cc9eead54f903fb6c1aff365b
+size 6863
diff --git a/t1/task_image/038/frame/038_002.png b/t1/task_image/038/frame/038_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..58048d7e71a8729057a1f41209f1c066486c1c0f
--- /dev/null
+++ b/t1/task_image/038/frame/038_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ea66647b82152a1c54cd6d4df418b28b217c1c9deb1fbb5407f3b98a466d10aa
+size 6680
diff --git a/t1/task_image/039/039.png b/t1/task_image/039/039.png
new file mode 100644
index 0000000000000000000000000000000000000000..5ce1383060440b45cfaeb8b9cd5aa395863bd217
--- /dev/null
+++ b/t1/task_image/039/039.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3114d0e2693814f746e6cbfac929a5027e765ec488115c7c49c6e3ff730a9298
+size 19289
diff --git a/t1/task_image/039/039.txt b/t1/task_image/039/039.txt
new file mode 100644
index 0000000000000000000000000000000000000000..f51e7f96a6292bde3f40f7bb9d0bf9411ae63191
--- /dev/null
+++ b/t1/task_image/039/039.txt
@@ -0,0 +1,82 @@
+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:
+039
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/039/039.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/039/frame/039_000.png, /xxx/ExeWorldBench/t1/task_image/039/frame/039_001.png, /xxx/ExeWorldBench/t1/task_image/039/frame/039_002.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/t1/task_image/039
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/039. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/039/039.py
+* /xxx/ExeWorldBench/t1/task_image/039/039.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/t1/task_image/039/frame/039_000.png b/t1/task_image/039/frame/039_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..e3099223bbe247727974129b7f79d4e364218bc7
--- /dev/null
+++ b/t1/task_image/039/frame/039_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c4fd81ca9d65a6d93b51f54dcc1d8d43120c3b11980c8f6e5818bb37e1435896
+size 3757
diff --git a/t1/task_image/039/frame/039_001.png b/t1/task_image/039/frame/039_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..17dcaadb895a4686eae2ea95e63ae92c205efedf
--- /dev/null
+++ b/t1/task_image/039/frame/039_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a9f5c73e57ab5734a0bdb1e82a7eb09d25c7340103db137d1e9b9351a82b026b
+size 5070
diff --git a/t1/task_image/039/frame/039_002.png b/t1/task_image/039/frame/039_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..f777f1fa5b7066434bdf990ca98780408e7227e4
--- /dev/null
+++ b/t1/task_image/039/frame/039_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:74e7b7e71019069f99bec0b11371b8badb4ac0069469174291a045aaa5da94c0
+size 5070
diff --git a/t1/task_image/040/040.png b/t1/task_image/040/040.png
new file mode 100644
index 0000000000000000000000000000000000000000..ea56cebfbb0b94b39673bf0ed3e465f9b3228715
--- /dev/null
+++ b/t1/task_image/040/040.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f2a1b337769971939d7b1c06cf14fa9589c5ee3895fb9f8b3e4d6e710c016bff
+size 16612
diff --git a/t1/task_image/040/040.txt b/t1/task_image/040/040.txt
new file mode 100644
index 0000000000000000000000000000000000000000..47975e978d3ed53ff03a4155af50b82936b1bc84
--- /dev/null
+++ b/t1/task_image/040/040.txt
@@ -0,0 +1,82 @@
+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:
+040
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/040/040.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/040/frame/040_000.png, /xxx/ExeWorldBench/t1/task_image/040/frame/040_001.png, /xxx/ExeWorldBench/t1/task_image/040/frame/040_002.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/t1/task_image/040
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/040. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/040/040.py
+* /xxx/ExeWorldBench/t1/task_image/040/040.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/t1/task_image/040/frame/040_000.png b/t1/task_image/040/frame/040_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..03a5278830c70186f6ad7196550d6733c29f6190
--- /dev/null
+++ b/t1/task_image/040/frame/040_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ac9248704ec312d26d0bcb6c9f28a1d85208779dfe0334482afdfeac98bc737d
+size 5016
diff --git a/t1/task_image/040/frame/040_001.png b/t1/task_image/040/frame/040_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..47e1c5251c58061e83bd3bfb960675290aaeac12
--- /dev/null
+++ b/t1/task_image/040/frame/040_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:83dfedae911a43c870c92007d8331a67ac8ca087f0a4b1f9e1a4491b7b857bec
+size 5385
diff --git a/t1/task_image/040/frame/040_002.png b/t1/task_image/040/frame/040_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..d329e5a0b89b865b55c25b53a35a07b232666c14
--- /dev/null
+++ b/t1/task_image/040/frame/040_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f3d174f7915ee17392d866006b9fefc6633aec12fe5555028248b5a47388ddf7
+size 4920
diff --git a/t1/task_image/041/041.png b/t1/task_image/041/041.png
new file mode 100644
index 0000000000000000000000000000000000000000..95c2ea02a145f158e24aec325f8cf4b58cb01fd6
--- /dev/null
+++ b/t1/task_image/041/041.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9d96c33ed005715e54ecc024101cd004e1ce27fc7dbcccd0b4e77a3b2551bf49
+size 20105
diff --git a/t1/task_image/041/041.txt b/t1/task_image/041/041.txt
new file mode 100644
index 0000000000000000000000000000000000000000..d176f220e2122f6ced8ecd8d2998292fb014f420
--- /dev/null
+++ b/t1/task_image/041/041.txt
@@ -0,0 +1,82 @@
+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:
+041
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/041/041.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/041/frame/041_000.png, /xxx/ExeWorldBench/t1/task_image/041/frame/041_001.png, /xxx/ExeWorldBench/t1/task_image/041/frame/041_002.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/t1/task_image/041
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/041. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/041/041.py
+* /xxx/ExeWorldBench/t1/task_image/041/041.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/t1/task_image/041/frame/041_000.png b/t1/task_image/041/frame/041_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..7056bbd8b4390dec4ae4bcd9e7145a4eeefa005a
--- /dev/null
+++ b/t1/task_image/041/frame/041_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1055e07ace53625fe1fbae8613adf62774ce24dfba87994e36876295494bd812
+size 5029
diff --git a/t1/task_image/041/frame/041_001.png b/t1/task_image/041/frame/041_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..31bca6c4535cc84d7a131facff11ea7623933ca1
--- /dev/null
+++ b/t1/task_image/041/frame/041_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3e134c99a0cae4002eaf103053ad7f7b45528d1cec63eba79b340f723fbd4c8d
+size 4657
diff --git a/t1/task_image/041/frame/041_002.png b/t1/task_image/041/frame/041_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..2d807cf8116a732edd17febfaf65928f9f5aadf2
--- /dev/null
+++ b/t1/task_image/041/frame/041_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:035ba31df09589f8bab5f0f50cad7924e5ffb810b5c26385d9304e77e8afe9f0
+size 4867
diff --git a/t1/task_image/042/042.png b/t1/task_image/042/042.png
new file mode 100644
index 0000000000000000000000000000000000000000..0860be5217682c034738f2b1a031625d39c895ce
--- /dev/null
+++ b/t1/task_image/042/042.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8748af07916268407b524d8c97d2404405b420cbee09c69c1d94128ca62bc3e1
+size 15508
diff --git a/t1/task_image/042/042.txt b/t1/task_image/042/042.txt
new file mode 100644
index 0000000000000000000000000000000000000000..18f48e2deb08742a99f2c5fc2e10e8bfb620b6a4
--- /dev/null
+++ b/t1/task_image/042/042.txt
@@ -0,0 +1,82 @@
+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:
+042
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/042/042.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/042/frame/042_000.png, /xxx/ExeWorldBench/t1/task_image/042/frame/042_001.png, /xxx/ExeWorldBench/t1/task_image/042/frame/042_002.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/t1/task_image/042
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/042. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/042/042.py
+* /xxx/ExeWorldBench/t1/task_image/042/042.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/t1/task_image/042/frame/042_000.png b/t1/task_image/042/frame/042_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..e6723503b0c0bf1231e5b85172e0790765248bac
--- /dev/null
+++ b/t1/task_image/042/frame/042_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6adb61269ebfec343b8ac1229b04652d554c8bf0ab1367a76b4b9b3e069b980f
+size 4471
diff --git a/t1/task_image/042/frame/042_001.png b/t1/task_image/042/frame/042_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..a4c73a3b485ac880a6bfbdbd2617a1bb17bc5d99
--- /dev/null
+++ b/t1/task_image/042/frame/042_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bcc046bf58457ac2d1d9edab82a223a2d68dcb8467f75121fc9a86bc37ab16f7
+size 4670
diff --git a/t1/task_image/042/frame/042_002.png b/t1/task_image/042/frame/042_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..7490281d74964f83ef8c9d3a075f7a372030701c
--- /dev/null
+++ b/t1/task_image/042/frame/042_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:949b5ca6182c974ebcb5aec95b0a98b2f224918dc489da69e3626898a5119b63
+size 4698
diff --git a/t1/task_image/043/043.png b/t1/task_image/043/043.png
new file mode 100644
index 0000000000000000000000000000000000000000..4392bc5c4e1f4c968d0d6bc79d924e57090c4df0
--- /dev/null
+++ b/t1/task_image/043/043.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a29b3254b09e0ba71a944fb3b64d58cd450b0f4e2852aca9d84945a752ff6630
+size 50688
diff --git a/t1/task_image/043/043.txt b/t1/task_image/043/043.txt
new file mode 100644
index 0000000000000000000000000000000000000000..13ecb9ddc95265a1cc6013901f7ae59fd96842b1
--- /dev/null
+++ b/t1/task_image/043/043.txt
@@ -0,0 +1,82 @@
+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:
+043
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/043/043.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/043/frame/043_000.png, /xxx/ExeWorldBench/t1/task_image/043/frame/043_001.png, /xxx/ExeWorldBench/t1/task_image/043/frame/043_002.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/t1/task_image/043
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/043. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/043/043.py
+* /xxx/ExeWorldBench/t1/task_image/043/043.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/t1/task_image/043/frame/043_000.png b/t1/task_image/043/frame/043_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..50619e107e6d284447b99c7e4e02cc7cd82f5704
--- /dev/null
+++ b/t1/task_image/043/frame/043_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:775762827b31617f46980071f2d903fb06762c5ee552b8cf682df9f1c86e2826
+size 6910
diff --git a/t1/task_image/043/frame/043_001.png b/t1/task_image/043/frame/043_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..b900945dce7f1cd0c2eaf9363f0fd83cd2a4704f
--- /dev/null
+++ b/t1/task_image/043/frame/043_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d25e2266d69fb6d1eead32030486dcf62b5718008582aaa0ee336fa7f2d5ca4f
+size 7116
diff --git a/t1/task_image/043/frame/043_002.png b/t1/task_image/043/frame/043_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..16aa4bdc38609dab0c6c18e671575268db317eb8
--- /dev/null
+++ b/t1/task_image/043/frame/043_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:176123b3ab71d0df11ffa433e48d56f0e638d4038f8e187e74a56b3ffbdc8135
+size 7388
diff --git a/t1/task_image/044/044.png b/t1/task_image/044/044.png
new file mode 100644
index 0000000000000000000000000000000000000000..b1b180765fec0105e949372e406282d977d81998
--- /dev/null
+++ b/t1/task_image/044/044.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:60250be4e4cb7d5db653ad5dec6a6e18b64181bad76d5831a15dce3f8706537a
+size 98184
diff --git a/t1/task_image/044/044.txt b/t1/task_image/044/044.txt
new file mode 100644
index 0000000000000000000000000000000000000000..2659622c9e82b101049bbe0aaa5140b99dfa36e1
--- /dev/null
+++ b/t1/task_image/044/044.txt
@@ -0,0 +1,82 @@
+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:
+044
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/044/044.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/044/frame/044_000.png, /xxx/ExeWorldBench/t1/task_image/044/frame/044_001.png, /xxx/ExeWorldBench/t1/task_image/044/frame/044_002.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/t1/task_image/044
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/044. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/044/044.py
+* /xxx/ExeWorldBench/t1/task_image/044/044.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/t1/task_image/044/frame/044_000.png b/t1/task_image/044/frame/044_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..f30e41a21866fac816dc0220217cdafa6b32adb7
--- /dev/null
+++ b/t1/task_image/044/frame/044_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4de2bd949dac85d87697c0fb15b5062382298f46730924ecd6b95845ff049d60
+size 18382
diff --git a/t1/task_image/044/frame/044_001.png b/t1/task_image/044/frame/044_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..e948dea448f3b259225940457676e934aa939a0f
--- /dev/null
+++ b/t1/task_image/044/frame/044_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:569176c1e961ee430b1eae8ad1c1f81575e47190c2316486e99f5a0d569195d0
+size 19257
diff --git a/t1/task_image/044/frame/044_002.png b/t1/task_image/044/frame/044_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..14cde4cbfc47c9bd237fcf64ee7df3dfc26f8a88
--- /dev/null
+++ b/t1/task_image/044/frame/044_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:582e5c6fd81cf8364a3b3b8dafd6ab24240b6fabfbb1ee699c9c637db6895fdf
+size 19473
diff --git a/t1/task_image/045/045.png b/t1/task_image/045/045.png
new file mode 100644
index 0000000000000000000000000000000000000000..aa44a3e396d13ce19fb0290eb87ba7a9d8deb1f9
--- /dev/null
+++ b/t1/task_image/045/045.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dbaee5b43fc7d9a3b7707b2265296d6f456b8447afcab10039795b00a10c6e67
+size 37470
diff --git a/t1/task_image/045/045.txt b/t1/task_image/045/045.txt
new file mode 100644
index 0000000000000000000000000000000000000000..d733900a2c4182630d16f56ac5e7fab2aa82f51f
--- /dev/null
+++ b/t1/task_image/045/045.txt
@@ -0,0 +1,82 @@
+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:
+045
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/045/045.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/045/frame/045_000.png, /xxx/ExeWorldBench/t1/task_image/045/frame/045_001.png, /xxx/ExeWorldBench/t1/task_image/045/frame/045_002.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/t1/task_image/045
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/045. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/045/045.py
+* /xxx/ExeWorldBench/t1/task_image/045/045.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/t1/task_image/045/frame/045_000.png b/t1/task_image/045/frame/045_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..95ff4a9711758f0a4407f2dc2e4734b1beb29019
--- /dev/null
+++ b/t1/task_image/045/frame/045_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:647183a0af544af2d7d43665d0af7cc77c98a48c7b1ac13721b38ef008c9f8fa
+size 7974
diff --git a/t1/task_image/045/frame/045_001.png b/t1/task_image/045/frame/045_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..465c7696f4bdab14338beb2b7142ba57d84e2d42
--- /dev/null
+++ b/t1/task_image/045/frame/045_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:08d996234a1e4a2e478a556b276e00acb8876298dc1f84c7a417b2a06d583947
+size 7838
diff --git a/t1/task_image/045/frame/045_002.png b/t1/task_image/045/frame/045_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..38002f40635f3115d371523be44a5ebb3742ef5b
--- /dev/null
+++ b/t1/task_image/045/frame/045_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:39681b7186135284d2e68c35fe3f630869bfca41bad4151544b973f03965c763
+size 7814
diff --git a/t1/task_image/046/046.png b/t1/task_image/046/046.png
new file mode 100644
index 0000000000000000000000000000000000000000..d5ab5cab90f75d2be69be6f6a4dc391ae29de7ec
--- /dev/null
+++ b/t1/task_image/046/046.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e953836799ed910e03eaf21a2dbec4003a056242d1f69348fbfa6128f33cb79d
+size 427718
diff --git a/t1/task_image/046/046.txt b/t1/task_image/046/046.txt
new file mode 100644
index 0000000000000000000000000000000000000000..295fc159c2b0bd7f326deba6464090ce16d75bab
--- /dev/null
+++ b/t1/task_image/046/046.txt
@@ -0,0 +1,82 @@
+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:
+046
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/046/046.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/046/frame/046_000.png, /xxx/ExeWorldBench/t1/task_image/046/frame/046_001.png, /xxx/ExeWorldBench/t1/task_image/046/frame/046_002.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/t1/task_image/046
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/046. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/046/046.py
+* /xxx/ExeWorldBench/t1/task_image/046/046.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/t1/task_image/046/frame/046_000.png b/t1/task_image/046/frame/046_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..81cf62f98c408a3e48fcc12c28b180eace267841
--- /dev/null
+++ b/t1/task_image/046/frame/046_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e9781197bf51bafd3c4cc76ce15a14d172adf05da51a1e7f68d8b033df39be18
+size 68541
diff --git a/t1/task_image/046/frame/046_001.png b/t1/task_image/046/frame/046_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..0e4767a5f621ed162712fc3c1c6301de7ef2f01b
--- /dev/null
+++ b/t1/task_image/046/frame/046_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c5bbe4fbde5c5e30c6bf1ae6e46693410c6b17ac34608b62971622712e78b099
+size 67657
diff --git a/t1/task_image/046/frame/046_002.png b/t1/task_image/046/frame/046_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..9758dae11ea135824cdb489d7943d71ae1962993
--- /dev/null
+++ b/t1/task_image/046/frame/046_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:78ec79badbff024c1dcb42202658abd04a8a7d78bccd6a73fd38c48f2cc4f8bc
+size 69069
diff --git a/t1/task_image/047/047.png b/t1/task_image/047/047.png
new file mode 100644
index 0000000000000000000000000000000000000000..709c1a36a2b827ec2184f5b00d3447c9ef9b813a
--- /dev/null
+++ b/t1/task_image/047/047.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bf4d785555a318ed1e88f4b97d00d2fc4c1a95a2d402eb2b987cbe41264de340
+size 347265
diff --git a/t1/task_image/047/047.txt b/t1/task_image/047/047.txt
new file mode 100644
index 0000000000000000000000000000000000000000..f0526c980926b5c0aa57291ae411ea09f3299e1e
--- /dev/null
+++ b/t1/task_image/047/047.txt
@@ -0,0 +1,82 @@
+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:
+047
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/047/047.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/047/frame/047_000.png, /xxx/ExeWorldBench/t1/task_image/047/frame/047_001.png, /xxx/ExeWorldBench/t1/task_image/047/frame/047_002.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/t1/task_image/047
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/047. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/047/047.py
+* /xxx/ExeWorldBench/t1/task_image/047/047.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/t1/task_image/047/frame/047_000.png b/t1/task_image/047/frame/047_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..5cb753a06d8c146ca8fe9bce6dcf9469204525d6
--- /dev/null
+++ b/t1/task_image/047/frame/047_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d03e499ca711d00169628ad5ff4455a703d82e2f3f71430633e9707df0278b98
+size 79783
diff --git a/t1/task_image/047/frame/047_001.png b/t1/task_image/047/frame/047_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..b5b2f6ea7fb7827817e9d5507e9ecd103d125a7b
--- /dev/null
+++ b/t1/task_image/047/frame/047_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:24814e667ef73f73caf969084bf99032ecfad8d17079a5da4d9fec4e518b4d20
+size 89497
diff --git a/t1/task_image/047/frame/047_002.png b/t1/task_image/047/frame/047_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..e623511e99323766bcd670450ab4496daeae3c4a
--- /dev/null
+++ b/t1/task_image/047/frame/047_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:04a7426abacf52bd115f079359d677a3bf5a9ec3bec104e16246af90397333f1
+size 95324
diff --git a/t1/task_image/048/048.png b/t1/task_image/048/048.png
new file mode 100644
index 0000000000000000000000000000000000000000..9bb0ebbd004313d0f17e876fa276af3470124595
--- /dev/null
+++ b/t1/task_image/048/048.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2db49d05caff459caabdc69c13a90282354811ca7e50d18d0bd4de792dcbcabb
+size 258802
diff --git a/t1/task_image/048/048.txt b/t1/task_image/048/048.txt
new file mode 100644
index 0000000000000000000000000000000000000000..5225f2437d578e31f1cdab3e98f5d2c6a58c30b6
--- /dev/null
+++ b/t1/task_image/048/048.txt
@@ -0,0 +1,82 @@
+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:
+048
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/048/048.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/048/frame/048_000.png, /xxx/ExeWorldBench/t1/task_image/048/frame/048_001.png, /xxx/ExeWorldBench/t1/task_image/048/frame/048_002.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/t1/task_image/048
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/048. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/048/048.py
+* /xxx/ExeWorldBench/t1/task_image/048/048.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/t1/task_image/048/frame/048_000.png b/t1/task_image/048/frame/048_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..86c6815b4f773ccbf7866bb0a58ab3372c71aa97
--- /dev/null
+++ b/t1/task_image/048/frame/048_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0198809e19c4b9aec80efff053b87e87e287202a830f790cfc63ac00fc44385e
+size 52465
diff --git a/t1/task_image/048/frame/048_001.png b/t1/task_image/048/frame/048_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..3970f25b683e5f65243b547162cb8c93b6a10ec0
--- /dev/null
+++ b/t1/task_image/048/frame/048_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c1a89b39f3d6c456a43c729d31f4866d90451b5e7d07a8d8c51a9a0dd549fe5d
+size 69766
diff --git a/t1/task_image/048/frame/048_002.png b/t1/task_image/048/frame/048_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..139b4f725b4f2a8441845a36604e558e4be5b097
--- /dev/null
+++ b/t1/task_image/048/frame/048_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0330cfec566b0c69a1d6b6811e1cc829309e74814abf6fd04b687cf93e0c2b6b
+size 70526
diff --git a/t1/task_image/049/049.png b/t1/task_image/049/049.png
new file mode 100644
index 0000000000000000000000000000000000000000..9888d1c3e629fc4d02baf609af688b16c51ee27b
--- /dev/null
+++ b/t1/task_image/049/049.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4086d8fcb30f5a324ee86ad9b73ec072824ead214717046163933017fa760692
+size 323864
diff --git a/t1/task_image/049/049.txt b/t1/task_image/049/049.txt
new file mode 100644
index 0000000000000000000000000000000000000000..7c33df4b0acba220f3fa535b928f3dd62a123ec7
--- /dev/null
+++ b/t1/task_image/049/049.txt
@@ -0,0 +1,82 @@
+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:
+049
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/049/049.png
+Motion reference frames available on the local filesystem:
+/xxx/ExeWorldBench/t1/task_image/049/frame/049_000.png, /xxx/ExeWorldBench/t1/task_image/049/frame/049_001.png, /xxx/ExeWorldBench/t1/task_image/049/frame/049_002.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/t1/task_image/049
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t1/task_image/049. 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 mechanical device.
+2. A sequence of ordered motion reference frames illustrating how the device is approximately intended to move.
+
+The reference image provides the mechanical structure and appearance of the device, while the motion reference frames provide additional cues about its approximate motion, motion range, and interactions between components.
+
+The motion reference frames provide approximate visual guidance rather than an exact specification of the device's trajectory, timing, or motion states.
+
+Your task is to infer the mechanical structure and complete physically plausible motion of the device from these visual inputs, and generate a Blender 5.2 Python script that reconstructs and executes the mechanism in Blender.
+
+The goal is not merely to reproduce the static appearance or imitate the provided motion frames, but to create an executable mechanical system that follows realistic mechanical structure and physical behavior.
+
+==================================================
+REQUIREMENTS
+==================================================
+
+1. Mechanical and Motion Correctness
+
+- The reconstructed system must preserve the key mechanical topology, connections, and kinematic relationships indicated by the visual references.
+- Use the ordered motion reference frames as approximate cues to infer the motion direction, motion range, relative movement, and interactions between components.
+- The provided motion frames should not be treated as exact specifications of object positions, trajectories, timing, or motion ranges.
+- All components must follow realistic and physically plausible mechanical behavior throughout the motion.
+- If the exact dimensions or motion details cannot be inferred from the visual inputs, reasonable approximations are allowed, as long as the core mechanical principle and intended behavior are preserved.
+- Visual appearance may be simplified, but mechanical correctness, motion correctness, and executability must not be sacrificed for visual similarity.
+
+2. Motion Must Arise from the Mechanism
+
+- The motion of the device must arise from its mechanical structure, physical constraints, contacts, gravity, and/or physically meaningful actuation.
+- Only an appropriate input component may be directly driven. All downstream components must move through mechanical connections, constraints, contacts, or other physical interactions propagated from the input.
+- The provided motion frames are approximate behavioral references for understanding the mechanism, not trajectories or target poses 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, or other purely visual tricks to fake mechanical execution.
+
+3. Complete Motion
+
+- The final animation must show the complete intended mechanical behavior inferred from the visual inputs, rather than only isolated poses or a partial segment of the motion.
+- For cyclic mechanisms, the animation must cover at least one complete motion cycle.
+- For mechanisms capable of continuous motion, the animation should cover a sufficient motion process and range to fully demonstrate the intended mechanical behavior.
+- The generated motion should follow the overall motion pattern indicated by the reference frames while remaining mechanically and physically executable.
+- An implementation that only visually matches several reference frames but fails to produce correct continuous mechanical motion between them is considered incomplete.
+
+4. Scene and Animation
+
+- The script must construct the mechanical device and produce a complete mechanical motion animation, rather than only a static scene or a sequence of manually matched poses.
+- The initial configuration of the mechanism must be physically reasonable and serve as a valid starting point for the complete mechanical motion.
+- The shapes, spatial relationships, and colors of major components should match the visual references as closely as reasonably possible.
+- Use a fixed camera and keep the entire mechanism visible throughout the animation.
+- Do not use camera motion, cropping, or viewpoint occlusion to hide incorrect mechanical behavior.
+
+5. Required Outputs
+
+Produce exactly two final artifacts:
+
+* /xxx/ExeWorldBench/t1/task_image/049/049.py
+* /xxx/ExeWorldBench/t1/task_image/049/049.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/t1/task_image/049/frame/049_000.png b/t1/task_image/049/frame/049_000.png
new file mode 100644
index 0000000000000000000000000000000000000000..cd7a6be818fddfa669b28c0fa85db21774165050
--- /dev/null
+++ b/t1/task_image/049/frame/049_000.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:87704ed2b47a327c880ecc67a2ff7553392e692d6a7d1041be991d40be44c56e
+size 51910
diff --git a/t1/task_image/049/frame/049_001.png b/t1/task_image/049/frame/049_001.png
new file mode 100644
index 0000000000000000000000000000000000000000..c1ac9bc9a1c7be7d1918a7418444afd7de8525f5
--- /dev/null
+++ b/t1/task_image/049/frame/049_001.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:42beb7e998743c86f60f3a06a9b5c6e2dc330ac74482604eb4cf0a4cdea5393e
+size 49395
diff --git a/t1/task_image/049/frame/049_002.png b/t1/task_image/049/frame/049_002.png
new file mode 100644
index 0000000000000000000000000000000000000000..baf62274f815d6aece77f85b84fa5437980ee8b4
--- /dev/null
+++ b/t1/task_image/049/frame/049_002.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b7b07b6a7367c26e3a1c8905b06507de9f5cc7c752ab3bf742333e1c2598c21f
+size 46999
diff --git a/t2/task/04_01/04_01.txt b/t2/task/04_01/04_01.txt
new file mode 100644
index 0000000000000000000000000000000000000000..1a41ffded4622400b4010ac864056e8632f6bd35
--- /dev/null
+++ b/t2/task/04_01/04_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:
+04_01
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/04_01/test_04_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/04_01
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/04_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/04_01/04_01.py
+* /xxx/ExeWorldBench/t2/task/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/04_01/test_04_01.png b/t2/task/04_01/test_04_01.png
new file mode 100644
index 0000000000000000000000000000000000000000..0b6628fe2b6d38f0ec21c23d09b6e0ef16e96492
--- /dev/null
+++ b/t2/task/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/04_02/04_02.txt b/t2/task/04_02/04_02.txt
new file mode 100644
index 0000000000000000000000000000000000000000..515382a174e31d35ce5227f83b3c7290226a4ed9
--- /dev/null
+++ b/t2/task/04_02/04_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:
+04_02
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/04_02/test_04_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/04_02
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/04_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/04_02/04_02.py
+* /xxx/ExeWorldBench/t2/task/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/04_02/test_04_02.png b/t2/task/04_02/test_04_02.png
new file mode 100644
index 0000000000000000000000000000000000000000..cd3eee9b1a18ad227a44891c935b3985277ff7f9
--- /dev/null
+++ b/t2/task/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/04_03/04_03.txt b/t2/task/04_03/04_03.txt
new file mode 100644
index 0000000000000000000000000000000000000000..0151a75b2e70c5ac9c87dda354b839f78fae4dba
--- /dev/null
+++ b/t2/task/04_03/04_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:
+04_03
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/04_03/test_04_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/04_03
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/04_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/04_03/04_03.py
+* /xxx/ExeWorldBench/t2/task/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/04_03/test_04_03.png b/t2/task/04_03/test_04_03.png
new file mode 100644
index 0000000000000000000000000000000000000000..c4fbfd85ef33635fd7187cfd5cb7890769b608d5
--- /dev/null
+++ b/t2/task/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/04_04/04_04.txt b/t2/task/04_04/04_04.txt
new file mode 100644
index 0000000000000000000000000000000000000000..be0bff038d8709375cce0cb128cebd8446a9253a
--- /dev/null
+++ b/t2/task/04_04/04_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:
+04_04
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/04_04/test_04_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/04_04
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/04_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/04_04/04_04.py
+* /xxx/ExeWorldBench/t2/task/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/04_04/test_04_04.png b/t2/task/04_04/test_04_04.png
new file mode 100644
index 0000000000000000000000000000000000000000..05679456e83ce1f7177d3b5b447859297638c91f
--- /dev/null
+++ b/t2/task/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/04_05/04_05.txt b/t2/task/04_05/04_05.txt
new file mode 100644
index 0000000000000000000000000000000000000000..04723b786628781a85c6f8104ac943e24a06bc6d
--- /dev/null
+++ b/t2/task/04_05/04_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:
+04_05
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/04_05/test_04_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/04_05
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/04_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/04_05/04_05.py
+* /xxx/ExeWorldBench/t2/task/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/04_05/test_04_05.png b/t2/task/04_05/test_04_05.png
new file mode 100644
index 0000000000000000000000000000000000000000..d671ede6ffee2893230e3974bab6e4769ff2f6a2
--- /dev/null
+++ b/t2/task/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/04_06/04_06.txt b/t2/task/04_06/04_06.txt
new file mode 100644
index 0000000000000000000000000000000000000000..c9bbc30462fa62cd878a3a79791805998c4b3a8d
--- /dev/null
+++ b/t2/task/04_06/04_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:
+04_06
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/04_06/test_04_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/04_06
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/04_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/04_06/04_06.py
+* /xxx/ExeWorldBench/t2/task/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/04_06/test_04_06.png b/t2/task/04_06/test_04_06.png
new file mode 100644
index 0000000000000000000000000000000000000000..d9977ca7a5838bf0e65734678a5faf030b091a25
--- /dev/null
+++ b/t2/task/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/04_07/04_07.txt b/t2/task/04_07/04_07.txt
new file mode 100644
index 0000000000000000000000000000000000000000..60caa86843f98c6513778ef7db5ab2f8be0b748f
--- /dev/null
+++ b/t2/task/04_07/04_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:
+04_07
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/04_07/test_04_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/04_07
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/04_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/04_07/04_07.py
+* /xxx/ExeWorldBench/t2/task/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/04_07/test_04_07.png b/t2/task/04_07/test_04_07.png
new file mode 100644
index 0000000000000000000000000000000000000000..dfa16378506539e0018c2f14a5a5c3ab5d69e769
--- /dev/null
+++ b/t2/task/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/04_08/04_08.txt b/t2/task/04_08/04_08.txt
new file mode 100644
index 0000000000000000000000000000000000000000..0746954ec8037e5a9d38bb528e869f03ec359b3d
--- /dev/null
+++ b/t2/task/04_08/04_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:
+04_08
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/04_08/test_04_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/04_08
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/04_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/04_08/04_08.py
+* /xxx/ExeWorldBench/t2/task/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/04_08/test_04_08.png b/t2/task/04_08/test_04_08.png
new file mode 100644
index 0000000000000000000000000000000000000000..7decf9087eb0f611b86c6a3f7dd4e2e042014fdf
--- /dev/null
+++ b/t2/task/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/04_09/04_09.txt b/t2/task/04_09/04_09.txt
new file mode 100644
index 0000000000000000000000000000000000000000..d200bcedbe9f67b867a3961eaa8dcf70039c5bb7
--- /dev/null
+++ b/t2/task/04_09/04_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:
+04_09
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/04_09/test_04_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/04_09
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/04_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/04_09/04_09.py
+* /xxx/ExeWorldBench/t2/task/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/04_09/test_04_09.png b/t2/task/04_09/test_04_09.png
new file mode 100644
index 0000000000000000000000000000000000000000..419792d8cb91b36e0dfb71f7193e8bbee0456805
--- /dev/null
+++ b/t2/task/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/04_10/04_10.txt b/t2/task/04_10/04_10.txt
new file mode 100644
index 0000000000000000000000000000000000000000..7c35ab20bc570a517b049592cd5f5fa36b416940
--- /dev/null
+++ b/t2/task/04_10/04_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:
+04_10
+
+Reference image available on the local filesystem:
+/xxx/ExeWorldBench/t2/task/04_10/test_04_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/04_10
+
+All artifacts for this task must be written inside /xxx/ExeWorldBench/t2/task/04_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/04_10/04_10.py
+* /xxx/ExeWorldBench/t2/task/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.