Blender assignMaterial: colour, idempotent slot, malformed colour refused #6
Loading…
Reference in a new issue
No description provided.
Delete branch "libby/blender-material-colour"
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 (/opt/commons/handoff/noka-mki-brokkr-20261110/gaps.md, G2): assignMaterial took no colour, so a palette could not be set through Brokkr. Commit
78ba4ea.What changed: assignMaterial accepts
color(RGB or RGBA); it sets the Principled BSDF Base Color and the material diffuse_color. A malformed colour fails naming the field before anything is created. Assigning the same material to an object twice adds no second slot. 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
python3 -I -m unittest discover -s tests -t testsin surfaces/blender: 113 tests, OK, 10 skipped (the skips need cultmesh_py / CULTLIB_PACKAGES; not run here).Not verified
🤖 Generated with Claude Code
Steward pass, 2026-11-10 (head after this note): replayed as one commit on main
6995eab(it was stacked on #5, now merged); the old commit cited above (78ba4ea) and the old test count (113) are superseded. Soul pass (separate agent) held on behaviour; findings fixed: colour limits now pinned (0 and 1 accepted; 1.0000001, -1e-9, 10**400 refused; four boundary mutants killed), a huge int no longer escapes the named refusal, color() and color_rgba() share one component rule, null documented as absent. 130 unit tests and 20 daemon tests pass locally. Not run: tests/live/material_colour.py and any real bpy behaviour (Blender not installed). Brokkr has no CI.78ba4eaf3dto0254fa7070