Drive the native app through its Wails MCP server

Every dev build compiles in Wails' own MCP server (ADR the-dev-build-compiles-in-the-wails-mcp-server-and-agents-drive-the-native-ui-through-it). It runs inside the app and executes against the real WKWebView: DOM queries, JavaScript evaluation, synthesized mouse and keyboard input with an animated on-screen cursor, window control, and event emit/wait. It is the only way to reach the page in the native app: the WebView is not inspectable, and macOS exposes its content to the accessibility tree as an empty scroll area.

Pick the loop before starting: