On 2026-09-12 I rescheduled 38 articles on this site with a single SQL statement. The JSON:API showed the new schedule straight away, and it kept showing it for 17 days. The Scheduler module, which is the thing that actually publishes them, never saw the change. It kept publishing on the old schedule the whole time.
A single line of JavaScript in this site's theme called a jQuery plugin that was never actually loaded, on every single page view, for just over ten months. Nobody was looking for it. It got deleted as a side effect of someone else's unrelated fix.
This site has two separate mechanisms for loading Google Tag Manager. One of them has never fired a single tag. The other was added by a tool that had no way of knowing the first one existed.
The same line of markup — a Google Fonts reference for Open Sans — went through four distinct states in one evening: deleted by accident, restored plainly, rewritten for performance, and finally replaced outright. Each stage is a real commit with a real, stated reason.
A CSS preload optimization shipped, ran on every page load, and did nothing. Not "did nothing dramatic" — did nothing at all, silently, for the length of time it took someone to notice the preload tags weren't matching anything a browser would actually reuse. The fix was two characters in a regular expression.
A script that was moved to run earlier on the page started throwing an error it had never thrown before. The fix that had made it "run early" and the bug that made it crash were the same change.
A theme library definition and its JavaScript file are both still sitting in this site's codebase right now, fully written, fully functional, and never loaded by anything. Not disabled, not commented out — just quietly disconnected from the one file that would tell Drupal to load them.
The same inline JavaScript snippet got moved to a different delivery mechanism three times in thirty minutes. Two of the three moves were blamed on an "& encoding" bug. Only the third move actually fixes the kind of bug that explanation describes — and checking the file at each step shows the first two blame something that isn't there.
Moving a template file from one directory to another shouldn't change what it renders. I moved html.html.twig to templates/layout/html.html.twig for Drupal 11 compatibility, and the rename quietly deleted an AdSense script tag and three Google Fonts links that had nothing to do with the move. Nobody noticed for hours.
The service account this site's automated pipeline runs under, api_publisher, is a small role: a handful of permissions in a YAML file, tracked in sync/ like every other piece of this site's configuration. Reading that file today tells you what it can do.