Currently if an end user is connected to the ez backoffice, and a devops enables a new bundle in the backoffice then clears all caches, the result is: the user does not see any change in the admin interface.

This feels counter-intuitive if you are coming from the non-spa world of ezpublish, where after a clear-cache command, all users would see the changes in the interface on next click (page load).
Otoh on ezplatform users never do full-page reload when clicking around, and their css/jss are thus never updated.

I suggest that a mechanism is introduced whereby a css/js reload can be triggered for already logged-in users, and hook it up to the 'clear all caches' event.