In one project, GeometryReader caused spacing to slowly creep over weeks. How did that even happen?

A SwiftUI project experienced gradual UI spacing issues over weeks due to accumulating geometry-derived values in state. Each GeometryReader recomputation added small incremental data that compounded over time. The solution was treating geometry as read-only input and avoiding long-term storage of derived spacing values, which immediately stopped the creep.