- Shipped
- August 3, 2026 at 4:48 AM UTC
- Author
- Kamo
- Commit
- 2df1938
MfaEnrollmentService shipped with @Service. Every Kamo service carries @ComponentScan("com.kamo"), so all of them construct it — but each declares its own EXPLICIT @EnableJpaRepositories list, and none included com.kamo.z.shared.mfa. That broke SecurityService's context and took down login. MediaService, DocsService, VOIPService, AIService and EmailService were armed to fail the same way on their next unrelated deploy; they had simply not rebuilt yet. Authentication belongs to SecurityService, so it declares the bean and nobody else pays for the scan. SharedLibBeanSafetyTest now fails the build on any NEW stereotype in this library that requires a Spring Data repository. This is the third occurrence of the same defect here — mlos.notification CrashLooped two earlier deploys, and the warning comments were already in the code when I shipped it again. A comment cannot fail a build; a test can. The guard found 29 pre-existing offenders across commerce and mlos. They are recorded rather than fixed: they ship today, so whatever makes them survive is empirically true, and untangling them during an outage would be reckless. The guard's job is to stop that list growing.