CodeClone b4: from CLI tool to a real review surface for VS Code, Claude Desktop, and Codex

I already wrote about why I built CodeClone and why I cared about baseline-aware code health. Then I wrote about turning it into a read-only, budget-aware MCP server for AI agents. This post is about what changed in 2.0.0b4. The short version: if b3 made CodeClone usable through MCP, b4 made it feel like a product. Not because I added more analysis magic or built a separate "AI mode." But because I pushed the same structural truth into the places where people and agents actually work — VS Code, Claude Desktop, Codex — and tightened the contract between all of them. A lot of developer tools are strong on analysis and weak on workflow. A lot of AI-facing tools shine in a demo and fall apart in daily use. For b4, I wanted a tighter shape: the CLI, HTML report, MCP, and IDE clients should agree on what "health" means the first pass should stay conservative deeper inspection should be explicit, not accidental report-only signals should stay visible without polluting gates setup failures sho