The browser can be driven, not just watched: a DevTools Protocol that mutates the real page

0.1.98 taught the engine to speak the standard DevTools protocol so a tool could inspect it. 0.1.100 lets a tool DRIVE it. Setting an attribute, removing a node, dispatching a key event, calling a function with arguments, or capturing a layout-aware snapshot of every node with its real on-screen box - these now change and read the engine's actual DOM, JS and layout state, not a mock. That is the command surface a headless automation tool (the kind behind end-to-end test runners) speaks, and it runs entirely in-process with no remote agent. The DevTools sub-score moves for the real driving capability; nothing that is not genuinely tested moves.