refactor(remote_config): move capability registration to feature modules

[watson]

What does this PR do?

Refactors remote config capability and handler registration to improve separation of concerns. Moves feature-specific remote config setup from a central location into their respective feature modules, following the same pattern already used by AppSec.

Key changes:

• Creates config/remote_config.js for client library config capabilities (APM_TRACING_*)
• Creates openfeature/remote_config.js for OpenFeature capabilities (FFE_FLAG_CONFIGURATION_RULES)
• Renames RemoteConfigManager → RemoteConfig and remote_config/manager.js → remote_config/index.js
• Simplifies proxy.js to instantiate RemoteConfig directly instead of through wrapper function

Motivation

Motivation

This refactoring establishes a clear pattern where each feature manages its own remote config capabilities and handlers together:

• Core features (like APM tracing) → always registered
• Optional features (like AppSec) → registered only when feature is enabled

OpenFeature is an exception to this pattern: it always registers the FFE_FLAG_CONFIGURATION_RULES capability (required by parametric tests since v5.72.0), but only registers its handler when config.experimental.flaggingProvider.enabled is true. This hybrid approach satisfies test requirements while keeping the experimental feature properly gated.

Additional Notes

Reviewing this PR:
The diff is large but mostly consists of code being moved between files. To review more easily:

1. File renames (no logic changes, just find/replace):

   • remote_config/manager.js → remote_config/index.js
   • test/remote_config/manager.spec.js → test/remote_config/index.spec.js
   • Class RemoteConfigManager → RemoteConfig (throughout)

2. New files with moved code:

   • config/remote_config.js - client library config capabilities moved from old remote_config/index.js + APM_TRACING handler moved from proxy.js
   • openfeature/remote_config.js - FFE capability + handler moved from proxy.js

3. Modified files:

   • proxy.js - Removed old wrapper, now instantiates RemoteConfig directly; handlers moved to feature modules
   • test/proxy.spec.js - Updated imports and assertions to match new structure

4. Assertion lib:

   • Replaced chai with node:assert/strict in remote_config tests for consistency

No functional changes to remote config behavior, purely structural refactoring.

[watson]

• refactor: move all config related code under config directory #7204
• feat(debugger): add Remote Enablement support #7137
• refactor(remote_config): move capability registration to feature modules #7127 👈 (View in Graphite)
• refactor(remote_config): move appsec-specific logic to appsec folder #7122
• refactor(remote-config): replace kPreUpdate with batch handler API (DEBUG-4402) #7121
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

Overall package size

Self size: 4.37 MB
Deduped: 5.19 MB
No deduping: 5.19 MB

Dependency sizes

| name | version | self size | total size | |------|---------|-----------|------------| | import-in-the-middle | 2.0.0 | 68.46 kB | 797.03 kB | | dc-polyfill | 0.1.10 | 26.73 kB | 26.73 kB |

_{🤖 This report was automatically generated by heaviest-objects-in-the-universe}

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-01-08 13:43:04

Comparing candidate commit 43e0e1e in PR branch watson/DEBUG-4402/even-more-rc-split with baseline commit 85edbfa in branch master.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 288 metrics, 32 unstable metrics.

[codecov]

Codecov Report

❌ Patch coverage is 97.61905% with 5 lines in your changes missing coverage. Please review.
✅ Project coverage is 84.54%. Comparing base (85edbfa) to head (43e0e1e).

Files with missing lines	Patch %	Lines
packages/dd-trace/src/remote_config/index.js	97.28%	5 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #7127      +/-   ##
==========================================
+ Coverage   84.53%   84.54%   +0.01%     
==========================================
  Files         528      529       +1     
  Lines       22538    22542       +4     
==========================================
+ Hits        19052    19058       +6     
+ Misses       3486     3484       -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[BridgeAR]

Should we cache this already? Potentially add a TODO entry for that?

[watson]

Do you mean cache the result of this.getPayload(), or? Then we need to deal with cache invalidation as it can change from request to request, but it's doable. But I would say outside the scope of this PR as this code is just moved from the old packages/dd-trace/src/remote_config/manager.js file. I've added a TODO for now