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-00217 Status
status: done
task: armature.autoside_names operator LOCAL_EXACT slice
updated: 2026-08-22 America/New_York
scope:
- The minimal fixture contains one armature with two selected bones on opposite sides of the X axis.
- Desktop runs `ARMATURE_OT_autoside_names(type='XAXIS')` with `poll=true` and `FINISHED`, naming the positive-X bone `.L` and the negative-X bone `.R`, then preserves both names through save/reopen.
- The existing Main reader exposes the same armature bone names; no new reader field, 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 persisted names and remain idempotent.
- WASM/Main observes the same `.L`/`.R` names for the same fixture, 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-00218`