Where did @Binding cause a bug that only showed up after a few releases?

A SwiftUI @Binding bug went undetected through multiple releases when refactoring renamed classes, breaking one write path while the UI appeared correct due to cached state. The issue surfaced days later through analytics discrepancies. The root cause was assuming binding symmetry, resolved by centralizing write permissions and adding assertions to catch missing paths early.