Continue Blender Web parity task handoff
This commit is contained in:
19
docs/status/M16-GAP-00234.md
Normal file
19
docs/status/M16-GAP-00234.md
Normal file
@@ -0,0 +1,19 @@
|
||||
# M16-GAP-00234 Status
|
||||
|
||||
status: done
|
||||
task: armature.delete operator LOCAL_EXACT slice
|
||||
updated: 2026-08-22 America/New_York
|
||||
|
||||
scope:
|
||||
|
||||
- The minimal fixture contains one armature with three unparented bones; only the middle bone starts selected and active.
|
||||
- Desktop runs `ARMATURE_OT_delete` in edit mode with `poll=true` and `FINISHED`, deleting the selected bone while leaving the other two bones unselected and preserving the result through save/reopen.
|
||||
- Main already exposes armature bone names, parent IDs, and selection state, so the same post-delete fixture is observable in WASM/Main without expanding other data-blocks, editors, or browsers.
|
||||
|
||||
evidence:
|
||||
|
||||
- The generator, desktop checker, npm comparator, direct comparator, malformed-input negative, save/reopen check, and task-context checks passed.
|
||||
- WASM/Main observes exactly the two remaining bones, rejects malformed Blend input without Main mutation, and keeps the armature stable across save/reopen.
|
||||
- Repeated checker runs recognize the already-deleted state and remain idempotent; Chromium-only policy was preserved and no Firefox/WebKit run was made.
|
||||
|
||||
nextTask: `M16-GAP-00235`
|
||||
Reference in New Issue
Block a user