Files
workinf_Blender_Wasm/docs/status/M14-01D.md
mes123456 380cbed4ff
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
Checkpoint web parity through Chromium input tasks
2026-08-19 10:39:03 -04:00

1.3 KiB

M14-01D Status

status: done
task: probe identity and GPU/OS adapter recording
updated: 2026-08-19 America/New_York
enablingTask: false
parityStateChange: false

Scope

The production Chromium probe records observed browser identity, OS kernel/runtime identity, hardware concurrency, WebGL2 vendor/renderer/version, WebGPU adapter identity, and cross-origin isolation. WebGPU is recorded as BLOCKED/WEBGPU_ADAPTER_UNAVAILABLE in this headless environment; the result does not claim WebGPU support. The report is bound to the exact worker/WASM asset hashes used by the probe and carries a canonical identity SHA-256.

Evidence

  • npm --prefix web run build passed.
  • npm --prefix web run test:probe-identity passed twice (one report-generation run and one frozen report verification run).
  • Checker output: probe-identity-ok version=151.0.7922.34 os=linux/x64 webgl2=PASS,webgpu=BLOCKED identity=3c6f898e1b6ffd39862505b8e7dde8fd29369204e1670a013859f74ccaf1c1eb execution=DISABLED next=M14-01E.
  • git diff --check passed.

Next Task

M14-01E: Chromium WebGPU fail-closed boundary. Firefox and WebKit are excluded by the project Chromium-only iron rule.

Rollback

Remove the probe checker, report, manifest, package command and this status/task entry; keep M14-01C as the queue tail.