Test whether a WebView-embedded viewer runs standalone via headless Chrome and CDP

To check if a page embedded in a native app's WKWebView can run in a plain browser, don't infer it from the code: serve its resource folder from a small Node HTTP server and drive headless Chrome over CDP using Node's built-in WebSocket and no puppeteer. Bridges guarded with window.webkit && ... simply no-op, so the page can load without the app. If a wasm parser runs in a worker and reads the file with synchronous XHR and Range headers, the server must return 206 with Content-Range. Serving same-origin also satisfies a CSP built on 'self' plus a custom app scheme, without editing it. Use Runtime.evaluate to call the page's open API and Page.captureScreenshot to confirm rendering, since a resolved promise alone proves nothing about drawing.