Document best practices for a monorepo containing multiple libraries & runnable apps that consume those libraries

I'm finding it extremely difficult to find information on best practices for a poetry monorepo that would house multiple library projects and runnable applications. In particular, information on how to configure an appropriate venv for the monorepo and on how the pyproject.toml files should look, from the root directory down through the libraries & apps, for a good developer experience in their IDE of choice as well as how to properly publish libraries such that builds of the apps correctly use the published libraries when being deployed.

Bonus points for providing an example git monorepo. I've begun one that's broken/incomplete/WIP at https://github.com/matthewadams/python-poetry-monorepo.

Even more bonus points for the poetry CLI to offer scaffolding functionality to initialize a monorepo with best practices via poetry init.

Start with the linked WIP example repository and the requested Poetry monorepo layout. Document guidance for virtual environments, pyproject.toml files, IDE use, and publishing libraries so deployed apps use the published packages; treat poetry init scaffolding as a separate optional scope.