Hold the shell's inputs between two engines instead of reaching released controllers

A visual choice made while no globe is attached (a style key, a Display control, a voice command) is queued and applied to the next engine's settings after it restored the address's view, so the person's choice wins; reads answer from the released settings. The globe reset and a location lookup started without a globe do nothing, and the map-source chips and camera buttons are unbound until the next globe binds them.

scripts/package-boundaries.json

@@ -1072,6 +1072,7 @@
       "src/layers/weather/imageryHost.js",
       "src/ui/layerBindings.js",
       "src/ui/displayBindings.js",
+      "src/ui/pendingVisualSettings.js",
       "src/ui/shellFacade.js",
       "src/ui/streetLevelControls.js",
       "src/ui/streetLevelPresentation.js",
@@ -3311,6 +3312,7 @@
       "src/ui/aircraftDisplay.js",
       "src/ui/layerBindings.js",
       "src/ui/displayBindings.js",
+      "src/ui/pendingVisualSettings.js",
       "src/ui/shellFacade.js",
       "src/voice/realtimePreferences.js",
       "src/voice/realtimeProtocol.js",