[No QA] Docs updates for E/A#96042 Search navigation suggestions

[MelvinBot]

Summary

Documents the new Search navigation suggestions added in #96042 (part of #92752).

That PR lets members jump to a top-level destination — Home, Inbox, Spend, Workspaces, or Account — by typing its name (or a go / go to prefix) in Search and selecting the Go to [destination] result.

The existing Navigating New Expensify article already documents these same five destinations via the navigation tabs, so this is the natural home for the new capability.

Changes

Updated docs/articles/new-expensify/getting-started/Navigating-New-Expensify.md:

• Added a new task-based section How to jump to a destination using Search describing how to open Search, type a destination name (or go / go to), and select the Go to [destination] result. Notes the three-character minimum and the alphabetical list shown for a bare go / go to.
• Added an FAQ entry: Can I use Search to move between sections of Expensify?
• Updated the description, keywords, and internalScope metadata to include Search-based navigation.

Scope notes

#96042 intentionally ships only the five top-level destinations and excludes Spend submenu, Account settings, Workspace settings, Domain, and Create/FAB suggestions. This doc update is scoped to match — only the shipped behavior is documented, and it can be expanded as later parts of #92752 land.

Authoring compliance

Written per docs/HELP_AUTHORING_GUIDELINES.md, docs/HELPSITE_NAMING_CONVENTIONS.md, and docs/TEMPLATE.md: single # title, task-based ## headings, sequential numbered steps, bold UI labels in exact Sentence case (Search, Go to [destination], and the five destination names), and an FAQ entry.

---

@nabi-ebrahimi, please review the files changed and confirm they reflect the current behavior. Then mark this PR Ready for review.

[OSBotify]

A preview of your ExpensifyHelp changes have been deployed to https://1ec3cd5f.helpdot.pages.dev ⚡️

Updated articles:

• articles/new-expensify/getting-started/Navigating-New-Expensify

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR makes a small, well-scoped addition to docs/articles/new-expensify/getting-started/Navigating-New-Expensify.md, documenting the new Search navigation suggestions. It adds one task-based ## section, one FAQ entry, and updates the description, keywords, and internalScope metadata. The changes are focused on a single, cohesive workflow and align well with the governance files.

Scores Summary

• Readability: 9/10 - Clear, concise steps; sequential numbered list; scannable. Minor redundancy between the new section and the FAQ answer (both restate the same five destinations and the go/go to prefix).
• AI Readiness: 9/10 - Task-based ## How to jump to a destination using Search heading with the feature name, question-style FAQ, #/## hierarchy only, and metadata (description/keywords/internalScope) all updated to reflect Search-based navigation.
• Style Compliance: 9/10 - Exact UI labels in bold Sentence case (Search, Home, Inbox, Spend, Workspaces, Account, Go to [destination]). Icon referenced parenthetically as "(the magnifying glass icon)". No prohibited vague navigation phrasing.

Key Findings

• New section heading is correctly task-based and starts with "How to" using the feature name (Search).
• Metadata was updated consistently across all three fields; internalScope still accurately states exclusions.
• FAQ entry follows the question format and points back to the same steps.
• Minor: the FAQ answer largely duplicates the new section body. This is acceptable but could be trimmed to a shorter answer plus reference.
• Minor: the PR description mentions a three-character minimum and an alphabetical list for a bare go/go to, but those details are not present in the doc body. Consider adding them if they aid users, or removing the claim from the PR summary.

Recommendations

• Optional: tighten the FAQ answer to reduce duplication with the new section.
• Optional: add the three-character minimum / alphabetical-list behavior to the section if it is user-relevant, to match the stated scope.
• No blocking issues; changes are compliant with the governance guidelines.

Files Reviewed

• docs/articles/new-expensify/getting-started/Navigating-New-Expensify.md - Compliant; minor optional improvements noted.

Note: Detailed line-by-line feedback has been provided as inline comments.

[github-actions]

Naming convention (exact UI label): **Go to [destination]** uses a bracketed placeholder in bold as if it were a literal button label, but Core UI Referencing Rules require the exact text shown in the product UI. Consider clarifying the dynamic label — e.g., "Select the Go to result for your destination (such as Go to Inbox)." so exact UI text is shown rather than a [destination] placeholder.

[github-actions]

Step formatting / readability: This step packs two distinct actions into one — typing a destination name AND the optional go/go to prefix. Per the Step Formatting Standard (single, clear, action-oriented steps), consider moving the go/go to alternative into a follow-up sentence or its own step so each numbered step is one action.

[github-actions]

Naming convention (exact UI label): **Go to [destination]** uses a bracketed placeholder in bold as if it were a literal button label, but Core UI Referencing Rules require the exact text shown in the product UI. Consider clarifying the dynamic label — e.g., "Select the Go to result for your destination (such as Go to Inbox)." so the exact UI text is shown rather than a [destination] placeholder.

[github-actions]

Step formatting / readability: This step packs two distinct actions into one — typing a destination name AND the optional go/go to prefix. Per the Step Formatting Standard (single, clear, action-oriented steps), consider moving the go/go to alternative into a follow-up sentence or its own step so each numbered step is one action.