[CPS] Refactor "Feature impacts" section for ga improvements

[shainaraskas]

Summary

fixes https://github.com/elastic/docs-content-internal/issues/1774

The original feature impacts section had four bullet points written when CPS was simpler. Since then, the landscape has grown beyond just dashboards, alerts, and visualizations, so the bullets were either redundant with better content elsewhere or incomplete for the current feature set.

Rather than expanding the bullets to cover every app, I slimmed the section to the two things that actually matter at this level (expanded dataset and user permissions) and cross-referenced the detailed pages. Painless scripting moved to the limitations snippet where it belongs.

The rules warning was added explicitly here because it's the one case that can trigger real-world actions on unexpected data.

Generative AI disclosure

1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?

• Yes
• No

[github-actions]

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

• Review docs changes (docs-review). Status: completed. View progress.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

[github-actions]

🔍 Preview links for changed docs

• deploy-manage/cross-project-search-config.md

[github-actions]

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

[github-actions]

Docs review summary

Focus areas

• Style and clarity: Rewritten section reads well overall — active voice, concise sentences, no Vale findings on modified lines.
• Jargon: No unexplained Elastic-internal jargon introduced; {{kib}}, {{cps-init}} etc. are used as defined product substitutions.
• Frontmatter and applies_to: No frontmatter changes in this diff; not applicable.
• Content type fit: The page remains a how-to/reference hybrid consistent with its existing structure; the new warning admonition and bullet restructuring fit the existing content type.
• Contradictions: No contradictions found against published docs (explore-analyze/cross-project-search-config overview and explore-analyze/cross-project-search.md remain consistent with the new "Feature impacts" wording).
• Parent issue satisfaction: Not applicable — no linked issue found in the PR description or closing keywords.

Notes

• One broken link anchor flagged inline in deploy-manage/cross-project-search-config.md — the new "Query syntax" bullet links to #cps-cap-as-the-default-behavior-for-linked-projects, which doesn't match the actual generated anchor for that heading.
• The painless-scripting move to deploy-manage/_snippets/cps-limitations-core.md preserves the cross-reference to #cps-painless-scripting in explore-analyze/cross-project-search.md, so no content was lost in the relocation.

Generated by Docs review agent for #8282 · copilot · sonnet50 · 175.6 AIC · ⌖ 21.1 AIC · ⊞ 16.4K