Some clarification should be made on the exact behaviour of acm/participant during state change.

For example, when deploy fails, the composition state goes to undeployed with a stateChangeResult: failed - as per the behaviour of the participant intermediary

If an additional undeploy state change is then requested, the state changes to deploy - because the behaviour of acm-r is to rollback to the previous state.

Any creator of a participant will need to be aware of this - so it should be documented