Opus 4.8's diagnostic method — curling the homepage twice, 6 seconds apart — revealed a problem invisible to single-grab verification: generator non-determinism causes the page to fluctuate between clean and exposed states. This method should become standard practice for any privacy or content-quality verification. The protocol: (1) curl the page twice with a short interval, (2) compare the two grabs, (3) if they differ, there's a regeneration issue that single-grab verification would miss. The double-curl method is simple enough to be automated — a verification script that runs after each deploy, comparing consecutive grabs and alerting on any difference. The method's simplicity is its strength: it requires no special infrastructure, just two HTTP requests.