When `actions.yaml` is staged during the build lifecycle (for example, in charms containing legacy or unenforced `actions.yaml` files staged from the project tree, or reactive charms generating actions), `PackageService.get_actions_yaml` now returns `False` so that craft-application's package file mediation leaves the staged and primed file untouched instead of unlinking it. ### Root cause In #2890, mediated packaging was introduced. When `actions.yaml` contained non-conforming syntax (e.g. in `tests/spread/smoketests/metafiles-bad-yaml-unenforced`), `preprocess.add_actions` did not populate `yaml_data['actions']`, leaving `project.actions` as `None`. `_get_mediated_yaml` therefore returned `None`, causing `_write_asset` to unlink `actions.yaml` from the prime directory. ### Solution Check if `actions.yaml` exists in the stage directory in `PackageService.get_actions_yaml()`. If present, emit debug and return `False`, leaving the file untouched in `prime`. ### Verification - Added unit test `test_get_actions_yaml_skips_when_exists_in_stage` in `tests/unit/services/test_package.py`. - Ran `make test-fast` (2849 passed). - Ran `ruff check`, `ruff format --diff`, and `ty check` (all passed).