1.7 KiB
M11-07 Status
status: done task: compositor allowlist CPU/WebGPU node goldens updated: 2026-08-17 America/New_York
Scope
The schema 1 WebGPU compositor allowlist contains only CONSTANT_COLOR, EXPOSURE,
INVERT, and COMPOSITE. A Blender 5.2 fixture supplies an independent constant,
exposure, invert, and integrated-chain scene through the production Main/WASM reader.
The production CPU executor and a real Chromium WebGPU compute pipeline must produce
identical LINEAR_SRGB Float32 RGBA bytes for every case.
Resource inputs, branching graphs, Viewer, Transform, Alpha Over, Blur, Mix, and undeclared Blender nodes remain outside the allowlist and fail before shader compilation. This task does not claim the M11-08 graph-preservation pipeline, HDR/color management parity, a production compositor scheduler, or server compositor execution.
Evidence
WEB_TEST_PORT=5562 npm --prefix web run test:compositor-node-golden: Node 3/3, Blender 5.2 Main/WASM fixture check, and Chromium WebGPU 1/1 passed.- The four CPU and WebGPU Float32 SHA-256 values match the committed golden exactly;
maximum absolute error is
0. - The first run without an isolated port passed Node/native checks but did not start Chromium because port 5173 was already occupied. It was not counted as evidence; the complete command was rerun on port 5562.
- Full regression passed: typecheck, lint, Node 171/171, production build, status
consistency, release evidence validation, and
git diff --check.
Rollback
Remove the WebGPU compositor plan/executor, M11-07 fixture/goldens/tests, and this status record; restore M11 to 6/14 and remove the N-020 WebGPU golden completed slice. Keep the existing bounded CPU compositor and Main graph reader unchanged.