Continue Blender Web parity task handoff
Some checks failed
M6 deployable RC / quick (push) Has been cancelled
M6 deployable RC / chromium (push) Has been cancelled
M6 deployable RC / release (push) Has been cancelled

This commit is contained in:
mes123456
2026-08-23 05:47:21 -04:00
parent 0a22992a13
commit 9f43244982
962 changed files with 60772 additions and 297 deletions

View File

@@ -0,0 +1,19 @@
# M16-GAP-00220 Status
status: done
task: armature.click_extrude operator LOCAL_EXACT slice
updated: 2026-08-22 America/New_York
scope:
- The minimal fixture contains one selected armature bone from `(0, 0, 0)` to `(0, 2, 0)` and a fixed cursor at `(1.5, 2.0, 1.0)`.
- Desktop runs `ARMATURE_OT_click_extrude` with `poll=true` and `FINISHED`, creating a connected `.001` child whose armature-space tail reaches the cursor and preserving it through save/reopen.
- The existing Main reader exposes the parent relationship, raw child coordinates, and rest matrix; the comparator derives the same armature-space endpoint without changing unrelated armature fields.
evidence:
- The generator, desktop checker, npm comparator, direct comparator, and task-context checks passed. Repeated checker runs recognize the persisted child and remain idempotent.
- WASM/Main observes the same two-bone hierarchy, preserves it across save/reopen, and rejects malformed Blend input without Main mutation.
- Chromium-only policy was preserved; no Firefox/WebKit run was made.
nextTask: `M16-GAP-00221`