Hi David,
I think yes. What Brandon was referring to is linking the process we use to refresh the container images and the rebuild of the ABI references, so one triggers the other. What happened with the failure was the container images got rebuilt, and that pulled in updates that change the ABI output (in valid ways), which then "look like" a failure or change from the reference that was previously saved off.
We save off older versions of the container images (i.e. things are tagged), so we can always roll back if need to. ABI reference generation should be deterministic on that container image, so we don't save "versions" of those references.
Cheers,
Lincoln