[MelvinBot]

Explanation of Change

Help site follow-up to #100570, which standardized the in-line delete experience for workspace rules.

That PR moved each rule editor's delete from a labelled Delete rule button at the bottom of the page to a trashcan icon in the top-right of the header. For most rule types the trashcan is gated behind the rulesRevamp beta and the labelled button still shows without it, so those help articles still describe what admins see today and are left alone. Agent rules are the exception: EditAgentRulePage dropped the footer button unconditionally, so every admin with the Custom agent beta now deletes an Agent rule from the header trashcan.

Create-Agent-Rules.md is the only article that documents that flow, so it is the only one updated here:

• Replaced "Click Delete" with the current two-step flow — click the trashcan icon in the top-right corner, then click Delete in the Delete rule confirmation.
• Documented that the trashcan icon only appears on a saved rule, matching the new canDelete gating.
• Fixed Agent Rules to Agent rules, the exact section name shown on the workspace Rules page (verified in the live app), per docs/HELPSITE_NAMING_CONVENTIONS.md.

Articles reviewed and deliberately not changed: Expensify-Card-Spend-Rules.md, Workspace-Rules.md, Workspace-Merchant-Rules.md, and Personal-Expense-Rules.md.

Fixed Issues

$ #100568
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.

This PR only changes a Markdown file under docs/articles. Suggested check: with the Custom agent beta enabled, open Workspaces > [Workspace name] > Rules, select a saved rule in the Agent rules section, and confirm the article's steps match what you see — a trashcan icon in the top-right corner, and a Delete rule confirmation with a Delete button.

• Verify that no errors appear in the JS console

Offline tests

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

---

@Krishna2323, 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.

[MelvinBot]

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

If you want to push updates to this branch yourself, run:

git remote add upstream https://github.com/Expensify/App.git
git fetch upstream melvin/docs-agent-rule-delete-100570
git checkout -b melvin/docs-agent-rule-delete-100570 upstream/melvin/docs-agent-rule-delete-100570
git push -u origin melvin/docs-agent-rule-delete-100570

That gives you the branch on your fork. If you'd rather own the PR outright, close this one and open a new one from your fork. Otherwise, review the change here and comment @MelvinBot mark this PR as ready for review when it looks right.

[OSBotify]

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

Updated articles:

• articles/new-expensify/ai-agents/Create-Agent-Rules

[stephanieelliott]

this was handled elsewhere