Mark the adverse-action clock's Spring constructor, so SecurityService boots

With a second (test) constructor and neither marked, Spring looked for a no-argument one and the new pods crashlooped; the older pods kept serving.

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.