Merge branch 'main' into 92752-shared-workspace-menu-source

Author: nabi-ebrahimi

.github/actions/javascript/isDeployChecklistLocked/index.js

@@ -9228,6 +9228,9 @@ const CONST = {
         VALIDATE_ACCOUNT: 'validate_account',
         REVEAL_CARD_DETAILS: 'reveal_card_details',
         REGISTER_AUTHENTICATION_KEY: 'register_authentication_key',
+        REPLACE_CARD: 'replace_card',
+        SHIP_CARD: 'ship_card',
+        REPORT_CARD_FRAUD: 'report_card_fraud',
     },
     EXPENSIFY_CARD: {
         FEED_NAME: 'Expensify Card',

Mobile-Expensify

@@ -111,8 +111,8 @@ android {
         minSdkVersion rootProject.ext.minSdkVersion
         targetSdkVersion rootProject.ext.targetSdkVersion
         multiDexEnabled rootProject.ext.multiDexEnabled
-        versionCode 1009045402
-        versionName "9.4.54-2"
+        versionCode 1009045500
+        versionName "9.4.55-0"
         // Supported language variants must be declared here to avoid from being removed during the compilation.
         // This also helps us to not include unnecessary language variants in the APK.
         resConfigs "en", "es"

android/app/build.gradle

@@ -456,6 +456,7 @@
         "americanexpressfdx",
         "bankofamerica",
         "Amina",
+        "anchorless",
         "androiddebugkey",
         "androidx",
         "apksigner",
@@ -484,6 +485,7 @@
         "autocorrection",
         "autodocs",
         "autofilled",
+        "autofocused",
         "automations",
         "autoplay",
         "autoreleasepool",
@@ -1031,6 +1033,8 @@
         "useblacksmith",
         "usernotifications",
         "utilise",
+        "vcfanzfav",
+        "vcfcitibank",
         "vcpu",
         "verticalanchor",
         "victoryaxis",

config/eslint/eslint.seatbelt.tsv

@@ -117,6 +117,21 @@ Deleting an Agent rule stops RuleBot from enforcing that rule on future report a
 
 ---
 
+## How to remove RuleBot from a workspace
+
+RuleBot enforces your Agent rules, so while a workspace still has Agent rules, RuleBot can't be removed, have its role changed, or be deleted. If you attempt any of these actions while Agent rules exist, Expensify blocks the action and shows a message prompting you to delete the Agent rules first.
+
+The following actions are blocked while the workspace still has Agent rules:
+
+ - Removing RuleBot from the workspace using **Remove from workspace** (from the **Members** list or RuleBot's member details page).
+ - Changing RuleBot's role to **Member** or **Auditor**. Promoting RuleBot to a **Workspace Admin** is still allowed.
+ - Deleting the RuleBot agent using **Delete agent** on the **Agents** page.
+ - Closing the RuleBot account.
+
+To remove, demote, or delete RuleBot:
+
+1. Delete every Agent rule in the workspace by following the steps to [delete an Agent rule](#how-to-delete-an-agent-rule) above.
+2. Once no Agent rules remain, remove RuleBot from the workspace, change its role, or delete the agent as needed.
 ## How to review Agent rule changes in the #admins room
 
 Whenever an Agent rule is added, updated, or deleted, Expensify records a system message in your workspace's **#admins** room so admins have a visible history of the change.
@@ -152,6 +167,10 @@ When evaluating a report, RuleBot can review the 50 most recent report actions,
 
 No. RuleBot is created automatically when you add your first Agent rule and is managed by Expensify.
 
+## Why can't I remove RuleBot from the workspace?
+
+RuleBot enforces your Agent rules, so it can't be removed, demoted, or deleted while the workspace still has Agent rules. Delete every Agent rule in the workspace first, and then you can remove RuleBot, change its role, or delete the agent.
+
 ## Where can I see a history of Agent rule changes?
 
 In the workspace's #admins room. Expensify posts a system message there each time an Agent rule is added, updated, or deleted.

cspell.json

@@ -108,3 +108,7 @@ Often, but not always. Expensify also compares additional receipt details, such
 
 Expensify may automatically review flagged duplicates in the background. If it determines the expenses are clearly not the same purchase, it dismisses the violation and adds a note that Concierge resolved the duplicate, with an **Explain** link describing why. If Expensify is not confident, the flag stays so you can resolve it manually.
 
+## Why do I see "You can only merge expenses on draft or outstanding reports"?
+
+You can only resolve flagged duplicates when the expense you're keeping is on a report in the Draft or Outstanding state. This message appears when that report is no longer editable — for example, it has been approved, closed, or reimbursed. Retract the report to make it editable again, then reopen **Review duplicates** and try again.
+

docs/articles/new-expensify/ai-agents/Create-Agent-Rules.md

@@ -1,7 +1,7 @@
 ---
 title: Use Search Operators to Filter and Analyze
 description: Learn how to use search operators, filters, and grouping to find, organize, and analyze expenses, chats, reports, and tasks in Expensify.
-keywords: [New Expensify, search operators, advanced filters, search rules, expense search, report search, chat filters, advanced search, group-by, view, chart, search syntax, bank account filter]
+keywords: [New Expensify, search operators, advanced filters, search rules, expense search, report search, chat filters, advanced search, group-by, view, chart, search syntax, bank account filter, custom field, international reimbursement IDs]
 internalScope: Audience is all Expensify members. Covers search operator syntax for filtering, grouping, and chart views. Does not cover saved search management or Search page UI navigation.
 ---
 
@@ -98,6 +98,9 @@ You can use the following operators to filter reports:
 - `withdrawal-type:` – reimbursement, expensify-card, or central-travel-invoicing
 - `paid-status:` – how the report was paid: `markedAsPaid`, `withdrawing`, or `confirmed`. Combine multiple values with commas, e.g. `paid-status:markedAsPaid,confirmed`
 - `action:` – blocking report action, e.g. `action:approve`
+- `submitter-user-id:` – Custom field 1 value set for the report submitter
+- `submitter-payroll-id:` – Custom field 2 value set for the report submitter
+- `order-deal-numbers:` – International reimbursement IDs on the report
 
 **Example query:**
 `status:paid exported<=2026-01-01 exported-to:xero`

docs/articles/new-expensify/reports-and-expenses/How-to-Find-and-Resolve-Flagged-Duplicate-Expenses.md

@@ -23,7 +23,7 @@
 	<key>CFBundlePackageType</key>
 	<string>APPL</string>
 	<key>CFBundleShortVersionString</key>
-	<string>9.4.54</string>
+	<string>9.4.55</string>
 	<key>CFBundleSignature</key>
 	<string>????</string>
 	<key>CFBundleURLTypes</key>
@@ -44,7 +44,7 @@
 		</dict>
 	</array>
 	<key>CFBundleVersion</key>
-	<string>9.4.54.2</string>
+	<string>9.4.55.0</string>
 	<key>FullStory</key>
 	<dict>
 		<key>OrgId</key>

docs/articles/new-expensify/reports-and-expenses/Use-Search-Operators-to-Filter-and-Analyze.md

@@ -11,9 +11,9 @@
 	<key>CFBundleName</key>
 	<string>$(PRODUCT_NAME)</string>
 	<key>CFBundleShortVersionString</key>
-	<string>9.4.54</string>
+	<string>9.4.55</string>
 	<key>CFBundleVersion</key>
-	<string>9.4.54.2</string>
+	<string>9.4.55.0</string>
 	<key>NSExtension</key>
 	<dict>
 		<key>NSExtensionPointIdentifier</key>