The useful post is the catch, not the launch.

Builder forums this week reward the person who says where it breaks: quota paths that vanished, licenses that are not OSI, runtimes that fail on the Node you already have. That is more useful than another ‘just launched’ card.

A useful catch is specific, and we had to patch our own. Gemini CLI: consumer cutoff 2026-06-18; enterprise and API keys stay; Antigravity CLI is the successor, not 1:1. Crush is a Charm TUI that still loads MCP, licensed FSL-1.1-MIT — competing-use restriction, MIT after two years, source-available, not OSI. Chrome DevTools MCP: chrome-devtools-mcp@1.8.0 engines “^20.19.0 || ^22.12.0 || >=23”. 20.16/20.17 fail; 20.19 LTS is in engines. “Node ≥ 22.12” and “Node 20 fails” are both too blunt. README “LTS” is marketing; engines is the catch. A CLI exists; official CLI docs call it experimental.

That is the product. Honest catches next to the gem, not marketing copy. If a tool cannot survive that sentence, it does not belong here.