Skip to content

Core

Shared App runtime stability

0.8.31

Keep App navigation on the selected route and remove repeated shared-runtime authorization reads.

  • Keep the App runtime view owned by the currently selected route. Late messages and navigation from a previous App frame no longer switch the launcher back and forth.

  • Batch imported release evidence, catalog identity, navigation metadata and actor grants under coherent reads. Current publication and authorization are still rechecked; this removes repeated per-execution reads without caching authority.

  • Production can import reviewed Developer release evidence while an active native portfolio keeps serving its pinned release IDs. Import is serialized with deployment changes and does not activate releases, change tenant installations or run migrations; a separately authorized group stage is still required.