SwiftUI streaming case study: layout hangs, stable anchors and local/cloud cancellation

I’m sharing a Swift-focused case study from the Ocarina guide I’ve been working on: The reproduced failure involved a transcript with changing-height streamed text and illustrated cards, lazy height estimation, a growing scroll target and animated scrolling. The observed process hung at roughly 99% CPU. The article covers replacing that transcript with a measured stack and stable fixed-height anchors, bounding UI publication frequency, rejecting stale updates by generation UUID and exchange ...