V8 type confusion in Google Chrome and Chromium

The repository contains four files: a GitHub Pages .nojekyll marker, disclosure and verification documentation in README.md, a styled verification interface in index.html, and the standalone trigger implementation in poc-core.js. Their listed sizes total 23,226 bytes; the original repository URL, git reference, and archive size were not supplied. The core exports CVE7971DOS in browsers and a CommonJS API for Node-based smoke testing. It constructs a small WebAssembly module, patches one floating-point immediate, imports a JavaScript callback and mutable global, and calls the exported main function. The documented defect is V8 Liftoff failing to spill all loop inputs before entering a loop, associated with fix commit 979757648854. On the claimed vulnerable arm64 build, the callback receives a malformed tagged value whose inspection can crash the renderer. A callback counter throws a normal JavaScript exception to terminate surviving runs. The wrapper displays browser identification and logs, documents automatic triggering, and exposes control, crash, desktop-x64, repeated-crash, multi-tab, stop, and evidence-copy controls. Visible handlers navigate to loop URLs and open additional tabs. LocalStorage markers retain trigger and loop state across page loads, so the README's blanket statement of no persistence is too broad: there is browser-local state, although no operating-system persistence mechanism is shown. No telemetry, exfiltration destination, or external service request appears in the supplied code; the page loads its relative core script. Important limitations: index.html is explicitly truncated, so its complete query parsing, stop handling, and crash-detection logic cannot be audited. The supplied MODES definitions give control and crash-x64 identical f32 and global bit patterns, so the x64 label does not select a distinct core payload and its claimed behavior is architecture-dependent rather than separately implemented. The code was not executed, and the claimed device results and fixed-version boundary remain repository assertions.