NestedNavigationGraphTileSchema

Hosts a self-contained Navigation 3 NavDisplay inside a tile, so a region of a screen can have its own back stack. The stack starts at startEntryId and every screen it can show is declared in entries.

Registration: on first composition the tile registers a NavigationController under navigatorId in the app's navigator holder — that id is how navigation events address this graph — and registers each Entry (its initial tiles/events, failure tiles/events and transitions) in the screen-extras holder. Both registrations are undone when the tile leaves composition, so the graph and its entries only exist while the tile is on screen. Each entry gets its own saveable state holder and ViewModelStore, so screen state survives navigating back and forth within the graph.

Transitions: for each navigation the per-entry Entry.transition, Entry.popTransition and Entry.predictivePopTransition win; when an entry does not define one, the graph-level defaultTransition / defaultPopTransition / defaultPredictivePopTransition apply; when neither is set the navigation is instantaneous (no enter or exit animation). The system back gesture pops this graph's own stack.

Triggers dispatched:

• OnNavigationEntrySetEventTrigger — fired whenever an entry is displayed, carrying the entry's screenId, so events can be wired per destination. It fires for the start destination too, and again whenever navigation returns to an entry.