[NO QA] Docs updates for E/A#88550 Add read-only conversation banner to chat FAQ

[MelvinBot]

Summary

• Updates the FAQ in the Chat Features and Moderation Tools help article to mention the new "This conversation is read-only" banner introduced in [Payment due @thesahindia] Show a read-only banner in ReportFooter instead of an empty footer #88550.
• Previously the FAQ only mentioned admin-only posting restrictions. Now it also covers the read-only conversation case.

Related PR

#88550

Test plan

• Verify the updated FAQ answer renders correctly on the help site
• Confirm the wording matches the actual banner text shown in the app

[melvin-bot]

@stephanieelliott looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR makes a single, focused change: it expands the FAQ answer for "Why can't I message in some rooms?" in Chat-Features-and-Moderation-Tools.md by adding a sentence about read-only conversations and the banner users will see. The change is small, targeted, and informative.

Scores Summary

• Readability: 8/10 - The added sentence is clear and describes both the condition (read-only conversation) and the visual indicator (banner text). The resulting sentence is somewhat long when combined with the existing text, but still scannable within an FAQ context.
• AI Readiness: 8/10 - The additional detail improves retrieval quality by introducing the phrase "read-only" and the specific banner text "This conversation is read-only," which aligns with real user search queries. Note: the file's YAML frontmatter is missing internalScope, which is required per the authoring guidelines -- however, that is pre-existing and outside the scope of this diff.
• Style Compliance: 9/10 - The language is precise and references the exact UI banner text. The banner text could be bolded (e.g., This conversation is read-only) to match the convention of bolding UI element text per naming conventions, but quoting it in the current form is still reasonably clear.

Key Findings

• The change correctly addresses a real user question: why messaging is unavailable in certain rooms beyond just admin-restricted permissions.
• The added sentence references specific UI text ("This conversation is read-only"), which supports deterministic writing and AI retrieval.
• Minor style note: the banner text is presented in quotes rather than bold formatting. Per HELPSITE_NAMING_CONVENTIONS.md, UI element text should use bold formatting rather than quotation marks.

Recommendations

• Consider changing "This conversation is read-only" to This conversation is read-only (bold, no quotes) to align with the button/UI element naming conventions that require bold formatting and prohibit quotation marks.
• No structural or heading changes needed -- the FAQ heading "Why can't I message in some rooms?" is already well-formed as a question-based heading.

Files Reviewed

• docs/articles/new-expensify/chat/Chat-Features-and-Moderation-Tools.md - Single FAQ answer expanded with read-only room context. Change is appropriate and well-scoped.

[github-actions]

Naming/style violation: The banner text "This conversation is read-only" is a UI element and should be bolded, not wrapped in quotation marks. Per HELPSITE_NAMING_CONVENTIONS.md, all UI labels must use bold formatting and must not use quotation marks.

Suggested fix:

Suggested change

	Rooms may have restricted posting permissions for Admins only. In other cases, the conversation may be read-only, and you’ll see a "This conversation is read-only" banner at the bottom of the chat.
	Rooms may have restricted posting permissions for Admins only. In other cases, the conversation may be read-only, and you'll see a **This conversation is read-only** banner at the bottom of the chat.

[OSBotify]

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.3.69-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

• Android
• iOS

[OSBotify]

🚀 Deployed to production by https://github.com/Beamanator in version: 9.3.69-18 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅