A check that looked for the wrong thing

Nothing about the site you visit changed in this release. Participant export and deletion stay unavailable, and the health page's storage warning is still deliberately visible. This note is about the project's own bookkeeping. The project regularly receives shared updates to its tooling from the studio. Because those updates overwrite files this project has also customised, there is a check that looks for customisations that were quietly wiped out. It worked by noticing when a file suddenly got much smaller. That turned out to be the wrong thing to look for. This time it flagged five files and every one of them was fine: they had simply been tidied up, with parts moved into smaller files alongside. Meanwhile a file that really had lost something was not flagged at all, because the update added far more than it removed and the file ended up bigger. Checking only for files that shrank meant the most likely case was the one never examined. The check now also compares what each file offers to the rest of the project before and after an update. If something other parts of the project rely on has gone, it stops and says which file and who was relying on it. If nothing relies on it, it says so and lets the work continue. The old size check was kept as well, since it has caught real problems before. While reviewing the rest of that update, three other checks turned out to be looking for exact wording rather than for the thing the wording described, and failed on code that was actually an improvement. Those now check the behaviour itself. A reminder the project had recorded as resolved was found to have quietly returned with the same update, so it has been reopened rather than closed again.