Comment 3 for bug 2064876

All right. Going over the problem again with John Meniel, revealed the detail where the devil should be hiding.

The pipeline is on Juju 3.1.6. Now, raising `secret-changed` event for the secret owner (in this case: the unit) was introduced in Juju version 3.1.7. (Which, or above must have been installed on local/AWS executions -- thus "all just worked".)

I'm double-checking whether the theory stands (right after my week of holidays).
But it's more than likely. Worries over the ticket could be suspended until :-)