Add Copy button to Concierge AI summary on help site

[MelvinBot]

Explanation of Change

Adds a "Copy" button to the Concierge AI summary panel on the help site (help.expensify.com). The button appears in the AI summary header next to the title, allowing support agents and users to easily copy the AI-generated response to their clipboard for sharing. After clicking, the button shows a green checkmark with "Copied" text for 2 seconds before reverting to the default state.

Changes:

• Added a Copy button to the ai-response-template HTML template
• Added copyAIResponse() JavaScript function using navigator.clipboard.writeText() to copy the AI content's text
• Added pill-style button CSS matching the existing ai-show-more button design
• Added copy.svg and checkmark.svg icon assets matching existing docs icon style

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/599634

Tests

1. Go to https://help.expensify.com
2. Search for any query (e.g. "how to submit an expense")
3. Wait for the Concierge AI summary to appear on the right side
4. Verify a "Copy" button with a copy icon appears in the AI summary header
5. Click the "Copy" button
6. Verify the icon changes to a green checkmark and the label changes to "Copied"
7. Paste in any text field and verify the AI summary text was copied correctly
8. Verify the button reverts to "Copy" after ~2 seconds

• Verify that no errors appear in the JS console

Offline tests

N/A — the help site is a static Jekyll site that requires a network connection. The copy button uses navigator.clipboard which is a local browser API and works regardless of network state once the page is loaded.

QA Steps

1. Go to https://help.expensify.com on staging
2. Search for any query
3. Wait for the Concierge AI summary panel to appear
4. Verify a "Copy" button appears in the header of the AI summary panel
5. Click the "Copy" button
6. Verify it changes to a checkmark with "Copied" label
7. Paste into a text field and confirm the AI summary text was copied
8. Verify button reverts to "Copy" state after ~2 seconds

• 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 verified there are no new alerts related to the canBeMissing param for useOnyx
• 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 shown in the product is localized by adding it to src/languages/* files and using the translation method
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • 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)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• 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)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• 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.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• 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

N/A — help site is web-only (Jekyll static site)

Android: mWeb Chrome

N/A — help site is web-only (Jekyll static site)

iOS: Native

N/A — help site is web-only (Jekyll static site)

iOS: mWeb Safari

N/A — help site is web-only (Jekyll static site)

MacOS: Chrome / Safari

N/A — screenshots will be added after manual testing

[MelvinBot]

I created this PR from an upstream branch since I don't have push access to your fork.

To take ownership of this branch and be able to push updates, run:

git remote add upstream https://github.com/Expensify/App.git
git fetch upstream claude-addCopyButtonToAISummary
git checkout -b claude-addCopyButtonToAISummary upstream/claude-addCopyButtonToAISummary
git push -u origin claude-addCopyButtonToAISummary

Then you can close this PR and open a new one from your fork.

[MelvinBot]

Fixed the failing Compress SVG check. The two new SVG files (checkmark.svg and copy.svg) were not compressed. Ran npm run compress-svg which lowercased hex color codes and applied minor path optimizations.

[OSBotify]

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

[rushatgabhane]

does not work