Forking a production SaaS is deceptively easy. The repository copies cleanly, the application starts, and the existing infrastructure still works. Then the inherited assumptions begin to show up. A route still describes the old product. An email contains the old identity. A reusable-looking component imports page-specific data. A new feature needs an exception because the original workflow was designed around a different user task. I ran into this while using a working AI generation app...