A case-sensitive check shipped a contradiction

What was wrong before this entry: the homepage counted six production systems while the About surface, one click away, said there was no production. Both statements were on the site at the same time. The second one was correct.

The label was changed to Shipped systems and the fix was checked with a search for the exact capitalised string. It came back clean, so the fix was recorded as complete. It was not. The lowercase form of the same phrase was still sitting in the site-wide meta description and in the Systems section header, and it shipped that way for one deploy.

The cure is two lines of discipline rather than two lines of code. A claim about meaning is never proven by a case-sensitive search — the same sentence exists in three capitalisations and a reader does not care which one they found. And a search that returns nothing is only evidence if it covered every route, not the one route where the change was made.

Both greps in the verification loop are case-insensitive now, and they run with untracked files included so a new file cannot hide a claim. The rule generalises past this site: a negative result from an incomplete search is not a negative result. It is an unchecked assumption wearing a command's clothes.