Default Blender workflow

Use this entry point for Blender tasks, alongside the task's geometry, animation and production skills. It grants no new paid, public, production, credential or customer-data authority. Do not change model routing or restart a gateway to use it.

Choose execution locally

Use a deterministic background script for a known-ahead build or long final render. For repeated inspect/edit cycles, prefer an installed, owned warm-session adapter with private pipes and isolated preferences. Load blender-warm-session when installed. Do not install an unreviewed DSH plugin, adopt an existing Blender GUI or expose a control port. If warm execution is unavailable, use the verified background-script route and disclose the fallback.

Keep one bounded resource owner, a whole-job deadline, an exclusive disposable workspace and explicit source/output identities. Preserve source files. Never detach a worker across turns. Blender exit success alone is not artifact acceptance.

Check before asking a model

Measure applicable geometry, materials, framing and lighting against the task specification. Unknown checks must be measured; failures return to the owning planner for a reviewed repair. Do not label an unperformed or inapplicable check as passed. Apply role-aware topology rules, not a blanket closed-solid assumption. Save native checkpoints before risky edits.

Use jevkit.blender.select(state) or pipe the closed JSON schema in docs/blender.md into jev blender-next. No scene files, screenshots, code, names, paths, free text or private measurements may enter this helper. The only permitted symptoms are its fixed vocabulary. private=true always bypasses inference.