docs(rms): clarify legacy mapping startup behavior

[jayzhudev]

This is a follow-up doc fix for #3812

Related issues

Supports #3593

Type of Change

• Add - New feature or capability
• Change - Changes in existing functionality
• Fix - Bug fixes
• Remove - Removed features or deprecated functionality
• Internal - Internal changes (refactoring, tests, docs, etc.)

Breaking Changes

• This PR contains breaking changes

Testing

• Unit tests added/updated
• Integration tests added/updated
• Manual testing performed
• No testing required (docs, internal refactor, etc.)

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: db0f73ae-1413-462f-87e0-118a88c82de5

📥 Commits

Reviewing files that changed from the base of the PR and between 00ec505 and 20a4432.

📒 Files selected for processing (1)

• dev/mac-local-dev/README.md

🚧 Files skipped from review as they are similar to previous changes (1)

• dev/mac-local-dev/README.md

---

Summary by CodeRabbit

• Documentation
  • Clarified how RMS evaluates node descriptor support during operations.
  • Updated guidance to explain that legacy mappings are best-effort and excluded from startup validation.

Walkthrough

The RMS node descriptor documentation now clarifies that legacy mapping is excluded from startup validation and descriptor support is evaluated when an operation executes.

Changes

RMS descriptor documentation

Layer / File(s)	Summary
Descriptor evaluation wording dev/mac-local-dev/README.md	Clarifies legacy mapping behavior and operation-time descriptor support evaluation.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the documentation-only change to clarify legacy mapping startup behavior in RMS.
Description check	✅ Passed	The description is clearly related to the documentation fix and matches the follow-up internal change described in the PR.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}