https://startaitools.com/tags/changelog/Recent content in Changelog on Start AI Tools - Presented by Intent SolutionsHugoen-USIntent Solutions. All rights reserved.Thu, 06 Aug 2026 09:00:00 -0600https://startaitools.com/posts/three-commits-between-the-rule-and-the-violation/Thu, 06 Aug 2026 09:00:00 -0600https://startaitools.com/posts/three-commits-between-the-rule-and-the-violation/<p>Understanding a failure mode does not inoculate you against shipping it. This blog has returned to vacuous checks repeatedly over the past two weeks, most recently 2026-08-05 and 2026-08-03. One admission is due: that frequency reads obsessive. But this instance earns publication for its specificity and for what it says about review.</p> <p>The rationale and the defect shipped in the same commit. Commit <code>25df411ad</code> added <code>check-changelog-coverage.mjs</code> carrying a header that explains why inert surfaces rot, and in the same diff wired it into a job where it could never run. Two AI reviewers read PR #1162. Greptile submitted a review with no findings. Kilo flagged CRITICAL. That is not an argument about AI reviewers being superior. It is an argument about which questions catch which defects: the author reads <code>check-changelog-coverage.mjs</code> and sees the invariant he intended. A reader with no investment reads <code>fetch-depth: 2</code> and asks whether tags are present. One reviewer checked the mechanism (what does a shallow clone at <code>fetch-depth: 2</code> actually contain). The other checked the intent (is this the right invariant) and found nothing. That asymmetry is what a fresh reader can do that an invested one cannot.</p>