Root navigator ↔ deep linking config: URL routing across nested navigators

Goal

Determine how a deep link received by the app is resolved to a screen inside a nested navigator when the linking prop is supplied only on the root navigator.

Constraints

• React Navigation v6 expects linking.screens with path and params defined before any child navigator components are rendered.
• Nested navigators inherit the linking object but do not automatically map URL segments to their own route keys without explicit screen entries.
• Android intent filters and iOS URL types must match the scheme, host, and path declared in the linking config; mismatches cause the JavaScript listener to fire without navigation.

Open questions

1. What is the correct ordering of the linking definition relative to the creation of nested navigators to ensure propagation?
2. How should linking.screens be structured so that a single URL pattern can target a screen deep inside a child stack or tab navigator?
3. Which native intent‑filter attributes (scheme, host, pathPrefix) must mirror the linking path to prevent silent drops?