Continue Blender Web parity task handoff
This commit is contained in:
18
docs/status/M16-GAP-00211.md
Normal file
18
docs/status/M16-GAP-00211.md
Normal file
@@ -0,0 +1,18 @@
|
||||
# M16-GAP-00211 Status
|
||||
|
||||
status: done
|
||||
task: anim.start_frame_set operator LOCAL_EXACT slice
|
||||
updated: 2026-08-22 America/New_York
|
||||
|
||||
scope:
|
||||
|
||||
- The minimal scene starts at frame 42 with a scene range of 1-120. The foreground animation-area context invokes `ANIM_OT_start_frame_set` (`poll=true`, `FINISHED`) and sets the scene start frame to 42.
|
||||
- The existing Main reader exposes the same scene frame tuple through `Scene.r.cfra`, `Scene.r.sfra`, and `Scene.r.efra`; no unrelated data-block, editor, or browser behavior was changed.
|
||||
|
||||
evidence:
|
||||
|
||||
- Desktop evidence records `FRAME_START_SET` and exact save/reopen. Repeated comparator runs preserve the fixture hash and report shape.
|
||||
- WASM/Main observes `{current: 42, start: 42, end: 120}` from the same fixture, preserves it across save/reopen, and rejects malformed Blend input without Main mutation.
|
||||
- The generator, npm comparator, direct comparator, and task-context checks passed. Chromium-only policy was preserved; no Firefox/WebKit run was made.
|
||||
|
||||
nextTask: `M16-GAP-00212`
|
||||
Reference in New Issue
Block a user