Blender add-on: exportGltf action #7
Loading…
Reference in a new issue
No description provided.
Delete branch "libby/blender-export-gltf"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Gap cut from the Noka MKI harness (G1): Brokkr had no glTF export action. Commit
3791667.What changed: new exportGltf action (filepath .glb or .gltf, optional extras, yUp, applyModifiers, selection). It mirrors renderStill path safety under the Render Output Directory preference: no overwrite, no links, no escape. Advertises asset.export.gltf. Docs updated.
Stacking: this branch sits on libby/blender-gn-recreation (PR #5, still open), so the diff against main also shows #5. The change itself is the commit(s) named above; review them with
git diff libby/blender-gn-recreation..HEAD. Merge #5 first.Verified
Not verified
🤖 Generated with Claude Code
Steward pass, 2026-11-10: replayed as one commit on main (it was stacked on #5), then merged with main after #6. Soul pass (separate agent): ~45 path probes through the real resolver found no escape from the render output directory; 22 hand mutants, survivors equivalent or covered by a second layer. Fixed from it: the selection is no longer read or written when none is given, and only view-layer objects are touched (an off-layer selection name is refused by name), because real Blender raises in select_set for them; docs now say texture sidecars of a .gltf and the check-to-write swap are not checked. 143 unit tests and 20 daemon tests pass locally (the old count in this body is superseded). Not run: tests/live scripts and the real exporter (Blender not installed), so the view-layer behaviour is reasoned from the Blender API, not observed. Brokkr has no CI.
379166799ctob3afd70cf9