The navigation bar should focus on the original option when select go back in the confirm changes dialog

[KarenChen-Linksys]

Steps:

1. Go to Menu > Any function that can change settings (e.g., Instant-Safety...).
2. Change settings and click on the other option on the navigation bar.
3. When the confirm changes dialog pops up, click on the "Go back".

Actual Result:
The navigation bar will focus on the option selected in step 2.

Expected Result:
The navigation bar should focus on the original option

Device
Pinnacle 2.0 FW: 1.2.2.26062820
Linksys Now Version: 2.5.0.700525

Screenshots

Additional context
log: log.txt
Video: https://github.com/user-attachments/assets/ad42cdff-0da1-4736-a3fc-790186a81468

[AustinChangLinksys]

🔍 Automated investigation (preliminary triage)

Line: 2.x / USP (TR-369)

Root cause:

• UI defect: the top navigation menu (TopNavigationMenu) renders its selection from AppChipGroup, whose visual selection is driven internally by the tapped index rather than by the actual route/selected prop. When the destination tap is blocked by the unsaved-changes dirty check (showUnsavedAlert → "Go back" → onExit returns false, so navigation is cancelled), the route never changes and widget.selected stays on the original page — but the chip's highlighted index has already moved to the tapped destination and is never reverted. Result: the highlight sits on the wrong (destination) option after cancelling.

Evidence (from source, dev-2.5.0):

• Dirty check cancels navigation but does not touch the menu highlight — lib/route/linksys_route.dart:

if (currentState.isDirty) {
  final bool? confirmed = await showUnsavedAlert(context);
  if (!context.mounted) return true;
  if (confirmed != true) {
    return false; // User cancelled, block navigation.
  }
}

• The menu highlight is computed only from widget.selected / tapped index; AppChipGroup owns the visual selection, and there is no re-sync back to widget.selected when navigation is blocked — lib/components/styled/menus/widgets/top_navigation_menu.dart:

final selectedIndex =
    widget.items.indexOf(widget.selected ?? widget.items.first);
...
selectedIndices: {selectedIndex},
onSelectionChanged: (selectedIndices) {
  if (selectedIndices.isNotEmpty) {
    widget.onItemClick?.call(selectedIndices.first);
  }
},

Confidence: High — code path confirmed on dev-2.5.0 (matches reported version 2.5.0.700525); pure UI state-sync defect, no backend error involved.

---

Auto-generated triage by Austin's tooling, pending Austin's review. Not a fix commitment.

[AustinChangLinksys]

Develop on dev-2.7.0