9.8Interview Talking Point

"Our framework treats skills and MCP as transports, not religions — which is Microsoft's own posture, since they ship both and recommend the CLI for coding agents at about 4x fewer tokens. The default is the Playwright CLI: snapshot once to discover the page as YAML on disk, then act by element refs at a few dozen tokens per command; when a ref goes stale we re-snapshot rather than guess. Playwright MCP stays in the stack for exactly one reason — surfaces without filesystem access, where inline state is the only option. And because browser.bind() lets both transports share one browser instance, routing per environment costs us nothing architecturally."