HOW KIRO FIXES ITSELF, AND HOW WE KEEP THE FIXES HONEST

Summary from the TLDR Dev newsletter

Kiro mines its own execution traces to find wasted effort and propose prompt or tool changes, while deterministic gates test improvements against fresh controls and a permanent regression suite. Seven fixes merged in the first week, and a compaction change raised internal retention scores from 0.82 to 0.92. The reported gains come from internal experiments, and every accepted change still requires human code review.