Add effective_config_hash keyword mapping to fleet-agents index

[juliaElastic]

Summary

Adds effective_config_hash and effective_config_label as a keyword field to the .fleet-agents index mapping and bumps FLEET_AGENTS_MAPPINGS_VERSION from 8 to 9.

This effective_config_hash field stores the SHA-256 hash of the OpenTelemetry collector's pipeline topology from the OpAMP effective configuration. It captures the functional shape of the pipeline (receivers, processors, exporters, connectors, service.pipelines, service.extensions) as a 64-character lowercase hexadecimal string, and is written by fleet-server when processing OpAMP check-ins.

The effective_config_label field stores a human-readable adjective-noun label (e.g. swift-hawk) derived from the first two bytes of the hash using two fixed 256-entry wordlists embedded in source. 65,536 possible combinations; stable across deployments and dependency updates since the wordlists are frozen in the codebase.

Companion PR: elastic/fleet-server#6872
Relates https://github.com/elastic/ingest-dev/issues/7064

Test plan

• Verify mapping version bump (8 → 9) triggers index template update
• Confirm effective_config_hash is indexed as a keyword and queryable/aggregatable

🤖 Generated with Claude Code

[elasticsearchmachine]

Pinging @elastic/es-core-infra (Team:Core/Infra)

[elasticsearchmachine]

Hi @juliaElastic, I've created a changelog YAML for you.

[github-actions]

🔍 Preview links for changed docs

⏳ Building and deploying preview... View progress

This comment will be updated with preview links when the build is complete.

[github-actions]

ℹ️ Important: Docs version tagging

👋 Thanks for updating the docs! Just a friendly reminder that our docs are now cumulative. This means all 9.x versions are documented on the same page and published off of the main branch, instead of creating separate pages for each minor version.

We use applies_to tags to mark version-specific features and changes.

Expand for a quick overview

When to use applies_to tags:

✅ At the page level to indicate which products/deployments the content applies to (mandatory)
✅ When features change state (e.g. preview, ga) in a specific version
✅ When availability differs across deployments and environments

What NOT to do:

❌ Don't remove or replace information that applies to an older version
❌ Don't add new information that applies to a specific version without an applies_to tag
❌ Don't forget that applies_to tags can be used at the page, section, and inline level

🤔 Need help?

• Check out the cumulative docs guidelines
• Reach out in the #docs Slack channel

[nchaulet]

🚀