### Bug Description see: https://github.com/juju/juju/issues/19207#issuecomment-2750556513 TLDR: if you (accidentally) pack a 'bundle.yaml' file with your charm, juju will attempt to deploy the bundle instead of the charm when doing `juju deploy ./mycharm.charm` Juju seems to think this is a feature and won't fix it, but I think at least charmcraft should validate that there is no 'bundle.yaml' file in your charm root, as I can guarantee you in 101% of the cases it will lead to unwanted and unexpected and hilariously confusing results. ### To Reproduce charmcraft init create a bundle.yaml in your charm root, put there any bundle. charmcraft pack juju deploy mycharm.charm - bundle gets deployed, not your charm. ### Environment all ### charmcraft.yaml ```yaml n/a ``` ### Relevant log output ```shell n/a ```