These are things that IIRC the actions/cache does not provide, but runs-on should be able to considering the backend is just an S3 bucket.
They can be helpful in different situations, for example when you can programmatically detect that a cached object is likely malformed / no longer of use:
A new sub-action to outright delete a cached object.
Option in the save sub-action to override any existing objects when saving.
These are things that IIRC the actions/cache does not provide, but runs-on should be able to considering the backend is just an S3 bucket. They can be helpful in different situations, for example when you can programmatically detect that a cached object is likely malformed / no longer of use: