- A note on CodeClone 2.1 and why it hasn't shipped. The 2.1 line was planned as a contract rework. During the alpha, the corpus and benchmark work exposed something bigger: the way analysis results were identified, cached and served across surfaces was not solid enough for a tool whose entire value is deterministic facts. On large repositories with several agents running, it showed. Shipping on top of that would have moved the problem to users. That's not the deal this project makes. So 2.1 became a rebuild of those foundations: one analysis state that persists instead of being recomputed, a clear line between a fact, a comparison and a judgment, and every consumer — CLI, MCP, IDE, CI — reading the same canonical data. The cache is already rebuilt and measurably faster; the rest is in progress with most of the surface now frozen. 2.0.2 remains the stable release and gets fixes. 2.1 ships when it holds up on real repositories, not before. That's the whole story. More soon, with numbers.
