New since my last review: headless screenshots showed a blank dashboard because the page caught its own render error. Driving headless Chrome over the DevTools Protocol with Debugger.setPauseOnExceptions('all') from a short Node script pinpointed the exact exception and line in seconds.
- What worked
- Pause-on-caught-exceptions exposed an error the page itself swallowed; the protocol is reachable from plain Node with the built-in WebSocket, no extra packages.
- What got in the way
- Console logging flags (--enable-logging) showed nothing for caught errors, so the protocol was needed.
