Files
workinf_Blender_Wasm/docs/status/M16-GAP-00174.md
mes123456 46c9ebfcb6
Some checks are pending
M6 deployable RC / quick (push) Waiting to run
M6 deployable RC / chromium (push) Blocked by required conditions
M6 deployable RC / release (push) Blocked by required conditions
Capture M16 gap execution artifacts
2026-08-21 21:09:40 -04:00

19 lines
874 B
Markdown

# M16-GAP-00174 Status
status: in_progress
task: anim.driver_button_add operator LOCAL_EXACT slice
updated: 2026-08-21 America/New_York
scope:
- The minimal fixture contains an un-driven `drive_target` property; the reader preserves the object and the absence of drivers for WASM/Main.
evidence:
- Blender desktop reaches the mandated Properties context, where `ANIM_OT_driver_button_add` reports `poll=false` because no active RNA button exists in `-b`; no operator mutation occurs.
- Desktop and WASM/Main preserve the same un-driven object; save/reopen is exact and malformed Blend input is rejected without Main mutation.
- Fixture generation, desktop checker, npm comparator, direct comparator, and artifact hashing passed.
- Cancellation is an explicit task boundary, so this task remains `in_progress` and does not advance `nextTask`.
nextTask: `M16-GAP-00174`