Fix back button loop on Profile after copiloting into an agent

[yusufdeveloper2903]

Explanation of Change

Copiloting into an agent from the agent chat header leaves 4 root stack entries, two of which hold owner-only screens guarded by withAgentAccessDenied. The redirect to Profile only dismissed the topmost modal, and because it started from the Reports tab linkTo's cross-tab rule turned the REPLACE back into a PUSH, discarding forceReplace. So the stale guarded routes survived underneath, and pressing back re-focused one, which fired redirectAgentAway and pushed Profile again — the loop.

Calling Navigation.popRootToTop() before the redirect drops every root entry created during the owner's session, so nothing guarded is left to re-fire and forceReplace can finally replace the guarded pane: root entries go 4 → 1, the split under Profile becomes [Settings_Root, Settings_Profile], and back lands on the Account page instead of Home. dismissModal is kept so the RHP still animates away, and linkTo is untouched. Added tests/navigation/AgentCopilotRedirectTests.tsx, which fails on main with Expected: 1, Received: 4.

Fixed Issues

$ #99074
PROPOSAL: #99074 (comment)

Tests

Precondition: an account with an agent created under Account > Agents.

1. Go to Account > Agents and tap the agent.
2. Tap Chat with agent.
3. Tap the chat header.
4. Tap Copilot into account.
5. Verify you land on the Profile page.
6. Tap the back button.
7. Verify the Account page opens and Profile does not reopen.
8. Repeat pressing back and verify you are never redirected to Profile again.
9. Regression (short path, [Due for payment 2026-07-23] Android & iOS - Back button on Profile opens Profile after copilotting into agent #94088): Account > Agents → tap the agent → Copilot into account → back → verify the Account page opens.
10. Regression (normal copilot): copilot into a regular member account and verify the current page is not reset and back behaves as before.

• Verify that no errors appear in the JS console

Offline tests

Copiloting is blocked while offline (useSwitchToDelegator short-circuits when the network is offline), so this flow cannot be started offline and the change has no offline-specific behavior.

QA Steps

Same as tests.

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (see Reviewing the code)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Before fix:

REC-20260909124538.mp4

After fix Native:

REC-20260909124657.mp4

Android: mWeb Chrome

REC-20260909130201.mp4

iOS: Native

After fix:

REC-20260909125401.mp4

iOS: mWeb Safari

After fix:

REC-20260909125617.mp4

MacOS: Chrome / Safari

[melvin-bot]

@eVoloshchak Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

[trjExpensify]

simple navigation fix 👍