- Shipped
- August 27, 2026 at 9:21 AM UTC
- Author
- Kamo
- Commit
- 6e0af42
The two rules generalise and both shapes exist elsewhere in this service, so the obvious next move is to widen the scan — and doing that would fail the build on six other people's packages the moment it landed. That is how a guard stops being trusted and starts being skipped, which the i18n one demonstrated earlier today. Widening it belongs to whoever is ready to fix what it finds in their own area, not to whoever notices it first. The class now says so, and carries the grep that answers the question without failing anyone. Also records BillingSetupService as a known instance that is correct: its self-invoked overload is reached across a bean boundary first, so it IS advised. It reads like a safety net without being one, and that file has already paid for the confusion once — every org created in a window got no subscription row because REQUIRED silently joined an already-committed transaction. Documented in place by its owner rather than changed. Comment only.