[HOLD Auth#22430] Surface AgentZero request ID in report action context menu

[jasperhuangg]

Explanation of Change

Adds a staging/dev-only report-action context menu item, "Copy AgentZero request ID", that copies the agentZeroRequestID stamped on AgentZero comments (from the companion Auth PR) so internal employees can trace an AI reply. It mirrors the existing non-prod "Copy Onyx data" item and reads the ID from the comment's originalMessage.

Fixed Issues

$
For https://github.com/Expensify/Expensify/issues/651179
PROPOSAL:

Tests

Requires the companion Auth PR deployed so AgentZero comments carry agentZeroRequestID.

1. Run the app in a non-production environment (dev or staging).
2. Open a chat where AgentZero/Concierge has posted a reply.
3. Right-click (or long-press) the AgentZero message to open the context menu.
4. Verify a "Copy AgentZero request ID" item appears.
5. Click it, then paste into a text field and verify the pasted value is the request ID.
6. Right-click a normal user message and verify the item does NOT appear.
7. On a production build, verify the item never appears.

• Verify that no errors appear in the JS console

Offline tests

1. Go offline.
2. Right-click an AgentZero message and click "Copy AgentZero request ID".
3. Verify the ID copies from already-synced Onyx data with no errors (no network required).

QA Steps

1. On staging, open a chat where Concierge/AgentZero has replied.
2. Right-click (or long-press) the AgentZero message.
3. Verify "Copy AgentZero request ID" appears and copies the ID to the clipboard.
4. Right-click a normal user message and verify the item does NOT appear.

• 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 any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • 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 any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• 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

[OSBotify]

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff

diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 1f2c159aad3..232d3e37294 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -840,7 +840,7 @@ const translations: TranslationDeepObject<typeof en> = {
         joinThread: 'Rejoindre la discussion',
         leaveThread: 'Quitter la discussion',
         copyOnyxData: 'Copier les données Onyx',
-        copyAgentZeroRequestID: "Copier l'ID de requête AgentZero",
+        copyAgentZeroRequestID: 'Copier l’ID de demande AgentZero',
         flagAsOffensive: 'Signaler comme offensant',
         menu: 'Menu',
     },
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 6bffb040d3a..bb83bbbf6ed 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -837,7 +837,7 @@ const translations: TranslationDeepObject<typeof en> = {
         joinThread: 'Entrar na conversa',
         leaveThread: 'Sair da conversa',
         copyOnyxData: 'Copiar dados do Onyx',
-        copyAgentZeroRequestID: 'Copiar ID de solicitação do AgentZero',
+        copyAgentZeroRequestID: 'Copiar ID da solicitação do AgentZero',
         flagAsOffensive: 'Sinalizar como ofensivo',
         menu: 'Menu',
     },

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

View workflow run

[codecov]

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines	Coverage Δ
src/CONST/index.ts	93.84% <ø> (ø)
...es/inbox/report/ContextMenu/ContextMenuActions.tsx	44.23% <14.28%> (-0.35%)	⬇️
... and 356 files with indirect coverage changes