didUpdateEffectiveGeometry reports outer display frame when app is send to background while using the inner display.

On iPhone Duo, when the app goes into background while being used on the inner display, windowScene(_:didUpdateEffectiveGeometry:) is called with a frame matching the geometry of the outer display.  When the app returns to the foreground, the callback fires again with the inner display geometry.
We reload our layouts based on this callback so the transient frame cause a visible relayout when returning to the app. This also reproduces when building with Xcode 27.3 beta and on OS version 27.2.0.

Snippet:

  func windowScene(_ windowScene: UIWindowScene,
                   didUpdateEffectiveGeometry previousEffectiveGeometry: UIWindowScene.Geometry) {
      log("didUpdateEffectiveGeometry", windowScene)
  }

  func sceneDidEnterBackground(_ scene: UIScene) { log("sceneDidEnterBackground", scene) }

  func sceneWillEnterForeground(_ scene: UIScene) { log("sceneWillEnterForeground", scene) }

  private func log(_ event: String, _ scene: UIScene) {
      guard let windowScene = scene as? UIWindowScene else { return }
      let state = windowScene.activationState == .background ? "background" : "foreground"
      let size = windowScene.effectiveGeometry.coordinateSpace.bounds.size
      print("\(event) | state: \(state) | size: \(Int(size.width)) x \(Int(size.height))")
  }

Logs:

  sceneDidEnterBackground    | state: background | size: 951 x 669
  didUpdateEffectiveGeometry | state: background | size: 466 x 678   <- outer display size, device NOT folded
  didUpdateEffectiveGeometry | state: background | size: 951 x 669
  sceneWillEnterForeground   | state: background | size: 951 x 669

Is this the expected behaviour, or a known issue? If it’s expected, what’s the recommended way to distinguish the effective geometry change?