Developer builds CI script to auto-validate tool counts across marketing docs

A developer behind the side project lans.cloud noticed that marketing materials — including launch articles, directory listings, and pitch emails — repeatedly showed outdated counts of the site's browser tools, even as the actual number grew to 100. The inconsistency went undetected for weeks because, unlike code, prose documents produce no errors when they contain wrong information. To fix this, the developer wrote an roughly 80-line script that derives the live tool count directly from the code registry and blocks any deployment if a living marketing document disagrees. Historical documents such as sent emails are deliberately exempt, since those figures were accurate at the time of writing. On its first two runs, the script caught a stale count and corrected mismatches across sixteen locations, validating the approach of treating marketing copy with the same rigor as production code.