Reduced out-of-catalog fixture · 1,000 nodes / 250 edits
Virtual-DOM diff and patch
Run one existing reduced VDOM engine against the deterministic 1,000-node tree and 250-edit transformation: hand-written JavaScript VDOM engine or authored linear-Wasm VDOM engine. Both targets calculate exact element insertion, attribute modification, tag replacement, reorder, and deletion patch lists.
This is not the full dom.vdom-diff-patch.v1 contract. That unavailable contract
requires 10,000 nodes and 2,000 edits. This page stays fixed at 1,000 nodes and 250 edits, leaves
frozen-v1 coverage at 0/38, and provides no performance ranking, corpus result, or general
engine claim.
Run in a fresh module worker
Unavailable: JavaScript and module workers are required to run this fixture.
Exact checks
Each run verifies the complete patch-tuple SHA-256 and exact node, depth, attribute,
tag-replacement, reorder, insertion, and deletion counters. In addition, the main thread
mounts real DOMHostAdapter elements into a hidden sandbox, applies the worker's
patch list, and asserts that the resulting canonical browser DOM string and SHA-256 match the
worker's expected output.
Lifecycle
Start creates a fresh module worker, keeping fixture generation and diffing off the main thread. Cancel, completion, error, navigation, or the fixed 120-second timeout terminates that worker. Token checks ignore stale messages.
Source and build
- Executed workload adapter
- Exact fixture generator
- JavaScript VDOM engine source
- Authored Wasm text
- Engine build manifest
- Commit-bound demo manifest
- Closed demo-manifest schema
The controls, fixed scope, source routes, and limitations are in this raw HTML response.
Limitations & Scope
- One deterministic 1,000-node tree and 250-edit fixture only.
- The full 10,000-node / 2,000-edit proposal contract is typed unavailable.
- No uploads, tree edits, persistence, result submission, or mutation route.
- No durations, rankings, accepted corpus evidence, or comparative conclusion.