Files
workinf_Blender_Wasm/docs/status/M16-GAP-00191.md
mes123456 9f43244982
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
Continue Blender Web parity task handoff
2026-08-23 05:47:21 -04:00

18 lines
1.1 KiB
Markdown

# M16-GAP-00191 Status
status: done
task: anim.keying_set_add operator LOCAL_EXACT slice
updated: 2026-08-22 America/New_York
scope:
- The minimal fixture contains one selected/active object with a custom `add_target` property and a three-key Action, but no scene Keying Sets. A foreground `VIEW_3D` context invokes `ANIM_OT_keying_set_add()` (`poll=true`, `FINISHED`), adding and activating one empty Keying Set without changing the Action.
evidence:
- Desktop evidence records Keying Set count `0→1`, an active newly-added set, unchanged `[1, 3, 5]` Action data, and exact save/reopen.
- WASM/Main reads the same fixture with the visible Action unchanged and save/reopen exact. The current scene snapshot does not expose Keying Set metadata, so the report explicitly records `keyingSetMetadata: NOT_EXPOSED_BY_SCENE_SNAPSHOT`; malformed Blend input is rejected without Main mutation.
- Fixture generation, foreground `VIEW_3D` checker, npm comparator, direct idempotent comparator, and artifact hashing passed. No production reader or protocol change was made.
nextTask: `M16-GAP-00192`