- Shipped
- 27 ஆகஸ்ட், 2026 அன்று 9:00 PM UTC
- Author
- Kamo
- Commit
- 65894df
BillingWormGuard, BillingDispatch and BillingSyncIssue each cite "a REVOKE UPDATE, DELETE in the KamoInitializer migration". No such migration existed — the statements were applied by hand when BL1's and MS1's DDL landed, so the live database is correct but the state was not reproducible. Entity @PreUpdate/@PreRemove guards do not fire for bulk JPQL or native SQL, so without these the append-only guarantee on a money event and on the record that a consumer texted STOP is convention rather than enforcement. Also carries the two partial indexes, which @Index cannot express.