- Ya
- 7 Agosti 2026, 07:42 UTC
- Mwandishi
- Kamo
- Ahadi ya
- bec6d86
The guard carried 29 baselined offenders and a location exemption, and caught none of the four outages it exists to prevent. Both were guesses standing in for a check: the exemption waved through everything under donotmodify, and the baseline recorded classes as "shipping today, so something must save them" without saying what. It now asks the actual question -- which package is this repository in, and is that package one every service scans -- and accepts the three idioms that survive a missing scan: ObjectProvider, @Autowired(required = false), and a @ConditionalOn* gate. That empties the baseline. 26 of the 29 were already behind @ConditionalOnProperty and were never at risk; MortgageProviderResolver had been converted to ObjectProvider, and its javadoc already described this exact failure. The last two, CommerceService and SubscriptionService, need commerce repositories -- and commerce is now genuinely universal rather than merely **************** since ChatService and CriticalFlowsService scan it too. A third test pins the escape hatches themselves, so a broken detector shows up as a failing assertion rather than as pressure to widen a baseline.