Docs updates for E/A#99460 vacation delegate missing workspaces invite step

[MelvinBot]

Explanation of Change

Help site follow-up for feat: Replace vacation delegate policy diff warning with RHP invite step, which replaced the blocking "policy diff" warning with an RHP step (VacationDelegateMissingWorkspacesPage).

docs/articles/new-expensify/settings/Delegate-when-out-of-office.md described the old behavior only — its FAQ said that when a delegate isn't part of your workspace, "Workspace Admins will be notified by email and prompted to add them," with no mention that you can now invite the delegate yourself. That answer is now incomplete and misleading, so the article needed an update.

What changed in the article:

• Added ## How to invite a Vacation delegate who is missing from a workspace, covering the new step: the two workspace groups (You are an admin of these workspaces: and You are a member of these workspaces:), the three possible button sets (Invite / Skip, or Confirm alone when you administer none of the listed workspaces), and the fact that leaving the page without choosing one leaves your delegate unchanged.
• Rewrote the assign steps to match the live flow: you select Vacation delegate on the Status page, search the Name, email, or phone number field, and the delegate saves as soon as you select them — there is no Save button on that page, which the old steps incorrectly told members to click.
• Rewrote the removal steps the same way: you reopen the Vacation delegate row and select your delegate again. The old steps described clearing a text field and clicking Save, which does not exist.
• Replaced the old email-only FAQ answer with one that reflects the new step, and added a Does skipping the invite still save my delegate? entry.
• Brought the file up to docs/HELP_AUTHORING_GUIDELINES.md: single # title plus # FAQ, task-based ## headings, added the required internalScope metadata, and used the UI-exact label Vacation delegate (lowercase "delegate") per docs/HELPSITE_NAMING_CONVENTIONS.md.

Every UI label in the article was verified against a live dev NewDot web session rather than taken from the source strings alone: the Account > Profile > Status path, the Vacation delegate row, the Name, email, or phone number field, the You are an admin of these workspaces: heading, and the Invite / Skip buttons. The absence of any confirmation prompt on removal was also confirmed live.

No other article needed changes. docs/articles/expensify-classic/copilots-and-delegates/Delegate-when-out-of-office.md documents Expensify Classic, which this PR does not touch, and the cross-link in Manage-Copilot-Access.md still resolves.

Fixed Issues

$
PROPOSAL:

Tests

// TODO: The human co-author must fill out the tests you ran before marking this PR as "ready for review"
// Please describe what tests you performed that validates your changed worked.

• Verify that no errors appear in the JS console

Offline tests

N/A — this PR only changes help site markdown.

QA Steps

// TODO: The human co-author must fill out the QA tests you ran before marking this PR as "ready for review".
// Please describe what QA needs to do to validate your changes and what areas do they need to test for regressions.

• 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 related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• 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

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

---

@war-in, please review the files changed and confirm they reflect the current behavior. Then post a new comment saying @MelvinBot mark this PR as ready for review.