Minor Description
In InteractionServiceDefault#preInteractionClosed() we currently call the `completeAndPublishCurrentCommand` first, and then later we loop around all transactionBoundaryAwareBeans callback, tell them to do their stuff. One of those is auditing (EntityChangePublishing).
I don't see any reason that command publishing is any different from auditing, so I think we should refactor to use the same callbacks..
Note that ExecutionPubilshing is not a transactionally aware aspect ... we publish that more eagerly, as each action invocation (or property edit) is executed .