Add itemized receipt changelog support and fix manual approval threshold bug

[MelvinBot]

Explanation of Change

This PR adds frontend support for the itemized receipt changelog action type and fixes a bug in the manual approval threshold message, to match the formatting changes made in https://github.com/Expensify/Web-Expensify/pull/51501.

Itemized receipt changelog:

• Adds UPDATE_MAX_EXPENSE_AMOUNT_NO_ITEMIZED_RECEIPT action type to CONST.ts
• Adds oldMaxExpenseAmountNoItemizedReceipt and newMaxExpenseAmountNoItemizedReceipt fields to OriginalMessage.ts
• Adds getPolicyChangeLogMaxExpenseAmountNoItemizedReceiptMessage function in ReportActionsUtils.ts (mirrors the existing NoReceipt version)
• Adds dispatch branches in PureReportActionItem.tsx and SidebarUtils.ts
• Adds English and Spanish translations for set/changed/removed itemized receipt required amount

Bug fix:

• Fixes getUpdatedManualApprovalThresholdMessage which checked typeof oldLimit !== 'number' twice instead of checking newLimit on the second clause. This meant newLimit was never validated, so if it was undefined, the function would produce incorrect output instead of falling back to getReportActionText.

Fixed Issues

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

Tests

1. Receive a POLICYCHANGELOG_UPDATE_MAX_EXPENSE_AMOUNT_NO_ITEMIZED_RECEIPT report action
2. Verify the changelog message displays correctly with the "itemized receipt required amount" wording in both the report view and sidebar
3. Verify set/changed/removed variants all display correctly
4. Verify the bug fix: a POLICYCHANGELOG_UPDATE_MANUAL_APPROVAL_THRESHOLD action with undefined newLimit now falls back to getReportActionText instead of showing "undefined"

• Verify that no errors appear in the JS console

Offline tests

N/A - these are display-only changes for server-generated report actions.

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 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 - display-only changelog text changes

Android: mWeb Chrome

N/A - display-only changelog text changes

iOS: Native

N/A - display-only changelog text changes

iOS: mWeb Safari

N/A - display-only changelog text changes

MacOS: Chrome / Safari

N/A - display-only changelog text changes

[OSBotify]

🦜 Polyglot Parrot! 🦜

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

The diff is too large to include in this comment (64KB), so I've created a gist for you:

📋 View the translation diff here 📋

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply, or directly by running gh gist view --raw 9c27610bbf21e417a9bf7815dedc1d42 | git apply 😉

View workflow run

[MelvinBot]

Fixed the Prettier check failure: import statements in SidebarUtils.ts and PureReportActionItem.tsx needed alphabetical reordering.

[MelvinBot]

Fixed the failing checks: added missing setItemizedReceiptRequiredAmount, changedItemizedReceiptRequiredAmount, and removedItemizedReceiptRequiredAmount translations to all 8 language files (de, fr, it, ja, nl, pl, pt-BR, zh-hans) that were causing TypeScript errors. The Prettier issue was already fixed in the previous commit.

[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.65% <ø> (ø)
src/libs/SidebarUtils.ts	80.84% <50.00%> (+0.23%)	⬆️
src/pages/inbox/report/PureReportActionItem.tsx	57.72% <50.00%> (-0.02%)	⬇️
...s/settings/Wallet/PersonalCards/AddNewCardPage.tsx	0.00% <0.00%> (ø)
src/libs/ReportActionsUtils.ts	55.34% <0.00%> (-0.35%)	⬇️
... and 58 files with indirect coverage changes

[MelvinBot]

All checks are now passing. The latest run shows every substantive check green — typecheck, ESLint, Prettier, all 8 test jobs, Storybook, iOS build, Android build, spellcheck, codecov, and CLA all pass. The only remaining item is perf-tests which is still in progress but is not blocking.

It's possible the checks were still running when you posted — the most recent push triggered a fresh CI run and everything completed successfully.

[MelvinBot]

The failing perf-tests check is unrelated to this PR's changes — it's a flaky infrastructure failure.

Evidence:

• All actual test steps passed (including "Run performance testing script" and "Validate output.json")
• The job failed during the "Complete runner" step (GitHub Actions runner cleanup), not during any test execution
• The same Reassure Performance Tests workflow is currently failing across many unrelated PRs (e.g., korytko/perf/pre-insert-search-under-rhp, VickyStash/refactor/33725-flashlist-with-inverted-flag, decompose/composer-pr2-activity-wrappers, root-tab-navigator, etc.)

You can re-run the check, but no code changes are needed.

[dangrous]

@MelvinBot please update the variable names to isOldLimitDisabled and isNewLimitDisabled instead of oldIsDisabled and newIsDisabled

[MelvinBot]

Renamed oldIsDisabled/newIsDisabled to isOldLimitDisabled/isNewLimitDisabled in the itemized receipt function (d5c0815).

[MelvinBot]

Fixed the failing typecheck.

Root cause: On `main`, `AddNewCardPage.tsx` was refactored from `useState`/`isModalVisible` to `useConfirmModal`, but a stale reference to `isModalVisible` was left on line 85 (``). When CI merges `main` into this branch, that broken reference caused `TS2304: Cannot find name 'isModalVisible'`.

Fix: Updated the branch's copy of `AddNewCardPage.tsx` to match `main`'s version with the stale `isModalVisible` prop removed from `SelectCountryStep`.

[MelvinBot]

⚠️ MelvinBot CI Fix Loop Detected

MelvinBot has made 5 consecutive commits trying to fix CI failures. Automatic CI fix dispatches are now paused for this PR.

Next steps: A human should review the recent commits and resolve the conflicting CI errors manually.