Publishing a PHP monorepo to Packagist with splitsh-lite

Ahnii! Series context: This is part 10 of the Waaseyaa series. Previous posts covered the entity system, access control, the API layer, DBAL migration, i18n, testing, deployment, and the AI packages. A framework that can't be installed isn't a framework. It's a demo. This post covers how waaseyaa went from a monorepo where every subpackage depended on @dev path repositories to individually versioned packages on Packagist. The Problem With "Just Publish It" Waaseyaa is a monorepo. The root composer.json defines 43 subpackages under packages/, each referenced as a path repository with @dev constraints. During development, this is convenient. Composer resolves everything locally, and you never think about versioning. The moment you try to register the root package on Packagist, the problem becomes clear. Packagist can't resolve path repositories. Every "waaseyaa/entity": "@dev" in a subpackage's require block points to a local directory that doesn't exist on the registry. The root package