Chrome DevTools MCP needs an acceptance chain
Today's Doramagic signal: `doramagic-chrome-devtools-mcp-pack` had 44 views, 120 clones, and 60 unique cloners in the partial 2026-05-22 GitHub metrics file.
The useful part is the path pattern. People opened traffic, commit activity, community health, pulse, branches, contributors, and README files.
That looks less like casual reading and more like an operability check.
For browser-agent work, the question is not only "can the agent click?" The real question is whether every step can be observed, verified, stopped at the right boundary, and recovered when the UI behaves differently.
Project page:
https://doramagic.ai/en/projects/chrome-devtools-mcp/
Source asset:
https://github.com/tangweigang-jpg/doramagic-chrome-devtools-mcp-pack
This is an independent Doramagic resource pack. It is not an official upstream project release unless the upstream project says so.