`exp-three-webgpu-core` now exposes a repo-specific scene readiness harness. It keeps the first graphics baseline deterministic while leaving room to swap in a real three.js build later.
The page measures capability state, scene load cost, and simple frame pacing from a wireframe-style orbit scene.
Scene Controls
Probe capability first, then run the deterministic scene baseline to record init and frame pacing metrics.
Viewport
Checks
Use one orbit camera path and fixed node count so frame pacing remains comparable across runs.
Keep the exported JSON structure stable before a real three.js renderer replaces this deterministic harness.
Record fallback state explicitly if WebGPU is unavailable.
Metrics
Environment
Activity Log
Schema-Aligned Result Draft
{
"status": "pending"
}
What This Unlocks
Custom Pages surface instead of the generic baseline probe
First graphics-specific raw JSON path for scene metrics
Stable capture target for later three.js/WebGPU integration