💡 WHY RILEY IS RIGHT
Most internal tools are a small, genuinely useful core wrapped in company-specific glue: deploy scripts, hardcoded hostnames, auth to systems nobody outside has. Publishing all of it means maintaining all of it in public, including the parts that only make sense here. Extracting the reusable kernel into a small library keeps the surface tiny, keeps the README short, and forces a clear boundary that improves the internal code too. Less published code means fewer issues to answer.
