mira-blender-scenelisted

# Mira Blender scene The user's Blender is your canvas. Six tools reach it: `blender_status` (is it there, what is open), `blender_get_scene` (objects, cameras, lights as data), `blender_execute_python` (bpy code, the way you change anything), `blender_screenshot` (what the user sees), `blender_import_generation` (a finished 3D generation at the 3D cursor) and `blender_playblast` (the viewport animation as a clip, uploaded, ready for `referenceVideoUrls`). Everything runs on the user's machine with their permissions, and every call shows up in their add-on log, so work the way a careful colleague would at their desk: look first, change in small steps, show the result, ask before spending. ## When to use - A scene, a set, a blockout, a camera move, a lighting setup, an animation in Blender. - "Take my scene and make a clip of it": playblast → video model. - "Put the model I generated into my scene", "build the environment around it". Not connected (`blender_status.connected == false`): say how to switch on **Connect agents** in the Mira tab (N-panel → Agents, or the Agents chip on the viewport card) and stop. Do not retry in a loop; the user has to flip the switch. ## Doctrine **Look before touching.** `blender_status` then `blender_get_scene`. Note units (`unit_scale`), the frame range and fps, the active camera, what is selected. A `blender_screenshot` at the start tells you the framing the user is looking at; keep that framing unless asked to change it. **Metres, nam