Extends both the `kubernetes` and `machine` profiles so that `charmcraft init` scaffolds a working example action alongside the existing lifecycle hook code, with unit and integration tests for it. The profile is a strong signal to human and agentic charmers for best practices. Including an example of an action is concrete input without needing the charmer to go find documentation, or have that in training data (human or model). The actions here were chosen from what charms in the wild actually declare, rather than invented. Across ~400 charms that declare actions, `pause`/`resume` is by a wide margin the most common pair in machine charms, and `restart` is the most common workload-lifecycle action in Kubernetes charms once the copy-paste families are discounted. ### Changes Both profiles in `charmcraft.yaml.j2`: Adds an `actions:` block with links to the charmcraft and Juju reference docs, matching the style of the existing `config:` block. In the `machine` profile, `pause` and `resume`: `pause` stops the workload and leaves the unit deployed in maintenance status, so an operator can take a unit out of service without removing it; `resume` starts it again. `src/workload.py.j2` gains a `stop()` stub alongside the existing `install()` and `start()`. In the `kubernetes` profile, `restart`: Restarts the Pebble service in the workload container, waits for the workload to be ready, and sets the unit active again. --- - [x] I've followed the [contribution guidelines](https://github.com/canonical/charmcraft/blob/main/CONTRIBUTING.md). - [x] I've signed the [CLA](http://www.ubuntu.com/legal/contributors/). - [x] I've successfully run `make lint && make test`. - [ ] ~I've added or updated any relevant documentation.~ - [ ] ~In documents I changed, I [added a meta description](https://canonical-starflow.readthedocs-hosted.com/how-to/add-a-page-meta-description/) if one was missing.~ - [x] I've updated the relevant release notes.