Reorganize Blender Web execution around capabilities
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

This commit is contained in:
mes123456
2026-08-24 18:37:46 -04:00
parent 0b2c3ba0dd
commit a081c68c87
2530 changed files with 763976 additions and 79 deletions

View File

@@ -0,0 +1,27 @@
# M16-GAP-00279 Status
status: done
task: asset.mark operator LOCAL_EXACT slice
updated: 2026-08-24 America/New_York
scope:
- The minimal fixture marks `WebGapAssetMarkObject` as an asset and persists the
author, description, and `operator-mark` tag. Blender desktop observes the
missing Asset Browser/editor context as `poll=false`, records `CANCELLED` for
`ASSET_OT_mark`, and confirms no Main mutation. Save/reopen preserves the
asset metadata exactly.
- WASM/Main reads the same object asset metadata through Scene IR with
`marked=true`, matching author, description, and tags. The comparator confirms
save/reopen stability and malformed-input rejection without Main mutation.
evidence:
- Fixture generation, Blender desktop checker, WASM rebuild, npm comparator,
direct comparator, and task-context handoff checks passed with exit code 0.
Chromium-only policy was preserved and no Firefox/WebKit run was made.
- The focused reader path exports asset metadata for object IDs and the Scene IR
protocol declares the corresponding optional `assetData` shape; no unrelated
data-block, editor, browser, or native-stub behavior was changed.
nextTask: `M16-GAP-00280`