Continue Blender Web parity task handoff
This commit is contained in:
19
docs/status/M16-GAP-00226.md
Normal file
19
docs/status/M16-GAP-00226.md
Normal file
@@ -0,0 +1,19 @@
|
||||
# M16-GAP-00226 Status
|
||||
|
||||
status: done
|
||||
task: armature.collection_remove operator LOCAL_EXACT slice
|
||||
updated: 2026-08-22 America/New_York
|
||||
|
||||
scope:
|
||||
|
||||
- The minimal fixture contains three bone collections, each initially retaining one distinct bone, with the middle collection active at index 1.
|
||||
- Desktop runs `ARMATURE_OT_collection_remove` with `poll=true` and `FINISHED`, removing the active collection, leaving its bone unassigned, and preserving the remaining collections through save/reopen.
|
||||
- The existing Main reader's collection indices and bone IDs provide the observable removal; no new data-block, editor, or browser behavior was added.
|
||||
|
||||
evidence:
|
||||
|
||||
- The generator, desktop checker, npm comparator, direct comparator, and task-context checks passed. Repeated checker runs recognize the already-removed collection and remain idempotent.
|
||||
- WASM/Main observes the same remaining collection order, member IDs, and unassigned removed bone, preserves them 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-00227`
|
||||
Reference in New Issue
Block a user