feat(blender): blender-run one-shot headless wrapper + FLEETTOOLS entry

scripts/blender-run launches each call as a docker run --rm of the Blender
image on fv-ml1 GPU 3, capped at 64g / 48 CPUs. It needs no desktop and does
not affect the GUI container's lifecycle. --job DIR stages a local directory
to /tank/blender/jobs/<name>/, runs Blender with that as the cwd, and copies
results back. It always passes --python-exit-code 1, because Blender otherwise
exits 0 when a --python script raises (measured).

Tested headless: Cycles GPU and CPU, EEVEE via EGL, Workbench, an STL
round-trip, and exit codes (3, 7 and 1 pass through). There is no STEP
importer. Written for draupnir's design work, and indexed in FLEETTOOLS with a
detail file.

docs/fleettools/FLEETTOOLS.md

@@ -76,6 +76,12 @@ live contract for its API. Fetch it rather than trusting a transcription.
   *When:* you need images rendered, or a character LoRA trained.
   *Detail:* `/home/lkraven/development/eshpfi-management/docs/fleettools/arbo.md`
 
+- **Blender** — Blender 5.2 LTS on fv-ml1 GPU 3 (borrowed, on demand). `scripts/blender-run` for
+  headless one-shot renders and conversions; `scripts/blender-mcp` for agent-driven scenes
+  (register per task).
+  *When:* 3D rendering, STL → image, scene building.
+  *Detail:* `/home/lkraven/development/eshpfi-management/docs/fleettools/blender.md`
+
 ## Working on the fleet itself
 
 - **elway** — SSH playbook runner for **CHANGING** things.