I built a 1-file CLI to catch .env drift before it causes production bugs

Almost every developer has fought .env issues. They're silent, annoying, and they only show up after you deploy or after someone clones the repo. Here's the exact failure I hit one too many times: I add STRIPE_KEY to my local .env. I ship code that reads process.env.STRIPE_KEY. I forget to add STRIP