docs(mongodb): split performance bullets and add LDAP cache

[brianamarie]

Summary

Restructures Performance and Reliability at Scale in products/mongodb/messaging.md so each bullet leads with a capability label before the colon, then carries the supporting detail after it.

Replaces the single Operational complexity bullet with three bullets:

• Faster recovery and replica sync (in-memory storage engine support, file copy-based initial sync)
• Steadier LDAP authentication (userToDNMapping caching for LDAP-backed auth)
• Automated backup and failover (Operator, Percona Backup for MongoDB, ExpertOps, existing PBM 2.13.0 evidence)

The ClusterSync migration bullet is unchanged.

Why

The prior operational-complexity bullet mixed HA recovery, LDAP behavior, and day-2 automation behind one broad label. Splitting keeps each colon label aligned to one buyer outcome and makes LDAP caching readable without a release version line.

Scope

• products/mongodb/messaging.md only
• No security-pillar or cross-product propagation
• No CVE, packaging, or newsletter copy in this PR

Reviewer notes

• LDAP caching is scoped to LDAP-backed authentication; the security bullet still owns the broader identity integration list.
• Wording follows present-state capability framing (no “8.0.21-9 adds” language).

Test plan

• Read all Performance and Reliability at Scale bullets for parallel colon-label pattern and tone
• Confirm no banned terms or em dashes
• Markdown lint / CI on the PR

Made with Cursor

[github-actions]

New File Governance Check

No added markdown files detected.

Doc Coverage Check

No new markdown docs detected.

Duplicate Detector

• Changed markdown docs: 1

No significant overlap detected.

Manual waiver commands (maintainers)

• /governance-ok all or /governance-all
• /governance-ok new-file, /governance-ok doc-coverage, /governance-ok duplicate
• /governance-reset all or /governance-reset with the same token

Waiver JSON is stored in a hidden PR comment (messaging-governance-waiver-data:v1), same pattern as Impact Check.

---

_{Triggered by pull_request. Workflow content-governance-checks.yml. Docs: AUTOMATION.md, automation/README.md.}

[github-actions]

Messaging Impact Check

• Changed files: 1

product-messaging-module-touch (WARN)

Product messaging modules often need checks against company framing and shared pillars or offerings.

Required review files:

• framework/core-positioning.md
• framework/why-percona.md

Suggested additional scan:

• use-cases-value-pillars/*.md
• offerings/*.md
• products/**/competitive.md

Manual waiver commands (maintainers):

• /impact-ok all (optional same-line note after all is ignored)
• /impact-all (same as /impact-ok all)
• /impact-ok <exact missing path>
• /impact-reset all
• /impact-reset <exact missing path>

Waiver state is stored in <!-- messaging-impact-waiver-data:v1 -->.

---

_{Triggered by pull_request. Workflow impact-check.yml. Docs: AUTOMATION.md, automation/README.md.}

[github-actions]

Messaging Smart Suggestions

File	Why impacted	Claim	Confidence
framework/core-positioning.md	Product messaging modules often need checks against company framing and shared pillars or offerings.	reliability	0.95
framework/why-percona.md	Product messaging modules often need checks against company framing and shared pillars or offerings.	reliability	0.95

Only auto-apply suggestions at high confidence with reviewer approval.

---

_{Triggered by pull_request. Workflow smart-suggestions.yml. Docs: AUTOMATION.md, automation/README.md.}

[brianamarie]

Consolidated into #143 to reduce reviewer load and context switching.