Hello UIKit team, When building custom multi-column layouts with UICollectionViewCompositionalLayout that must dynamically span or split across the iPhone Duo's .division reserved region during continuous hinge motion: What is the recommended strategy for handling UICollectionViewLayoutInvalidationContext during live fold/unfold gestures? Specifically, does the system coalesce intermediate trait changes (registerForTraitChanges) to allow smooth orthogonal scrolling without constantly purging cached layout attributes or triggering full cell rebinds? When adapting custom container view controllers using viewWillTransition(to:with:), should we coordinate layout updates through the UIViewControllerTransitionCoordinator's animate(alongsideTransition:), or does UIKit provide a dedicated layout guide / accessory pipeline that guarantees zero hitch when the trailing/leading safe area insets flip dynamically around the physical crease? Thanks!

Hello team, When configuring an AVCaptureMultiCamSession or consuming the new Virtual Front Camera, what is the recommended architecture to avoid frame drops or pipeline rebuilds (AVCaptureSessionRuntimeError) during dynamic posture transitions (from folded to unfolded / half-open)? Specifically: Does the Virtual Front Camera handle the lens handover internally with continuous timestamps in CMSampleBuffer, or does the underlying device switch trigger a device disconnect/reconnect notification that requires re-attaching inputs? How are the optical intrinsics (matrix_float3x3) and lens distortion coefficients updated through the hinge motion? Can we rely on continuous metadata attachments on each frame during the transition, particularly if running real-time CoreML / Vision processing? Thanks!

Hello SwiftUI team, When building custom container layouts conforming to the Layout protocol that dynamically flow content around the new .division reserved region (avoiding the fold area), what is the expected performance contract during rapid physical hinge movement? Does the continuous hinge motion invalidate the layout cache (makeCache / updateCache) on every frame, or are intermediate hinge angles decoupled from container re-measurements (sizeThatFits) to prevent layout thrashing? For asymmetric safe areas across the inner dual-pane presentation, what is the canonical way for a custom Layout to read the reserved division bounds directly from LayoutSubviews / subview.layoutPriority, without having to wrap each subview in a GeometryReader or an explicit ArrangementView that could disrupt matchedGeometryEffect transitions across the fold? Thanks!