@@ -284,6 +284,15 @@ const SettingsContentStack = createNativeStackNavigator({
284284 title : "Diagnostics" ,
285285 } ,
286286 } ) ,
287+ // Deliberately the one settings screen with no `linking:` path. Its params
288+ // are a tap-time snapshot, not a stable resource address: `now` is the
289+ // wall-clock of the tap, `environmentIds` is the usage screen's local
290+ // filter selection, and the window id/kind identify freshly aggregated
291+ // pools. React Navigation round-trips non-path params through the URL as
292+ // query strings, so a path here would bake in a permanently stale
293+ // timestamp and filter. The deep linkable surface is the list at
294+ // `settings/usage`, which rebuilds this state and pushes the detail from a
295+ // tapped account segment.
287296 SettingsUsageAccount : createNativeStackScreen ( {
288297 screen : UsageLimitAccountScreen ,
289298 options : { title : "Account" } ,
@@ -649,6 +658,14 @@ const RootStackConfig = createNativeStackNavigator({
649658 linking : `${ THREAD_LINKING_PREFIX } /attachments/:attachmentId` ,
650659 options : SOLID_HEADER_OPTIONS ,
651660 } ) ,
661+ // Deliberately the one root route with no `linking:` path. The route
662+ // carries zero params: its content is a session object (staged model,
663+ // provider groups, and live update callbacks) that the active
664+ // ThreadComposer presents into ExistingThreadSettingsRouteProvider before
665+ // pushing this screen — state no URL can reconstruct. Reached without a
666+ // presented session the screen navigates straight back, so a path would
667+ // only produce a flash-and-dismiss link. Deep links to a thread land on
668+ // `threads/:environmentId/:threadId`, where this sheet is one tap away.
652669 ThreadSettingsSheet : createNativeStackScreen ( {
653670 screen : ExistingThreadSettingsRouteScreen ,
654671 options : {
0 commit comments