Replace long-lived DD_CI_VIS_API_KEY by short-lived credentials via dd-sts-action

[xlamorlette-datadog]

Description

Migrate the long-lived DD_CI_VIS_API_KEY secret to short-lived credentials from dd-sts.

This is done with a new local composite action, .github/actions/dd-sts-credentials, which uses DataDog/dd-sts-action.

Additional Notes

By the way, small amendment in agents intsructions.

Jira ticket: IDMPL-808 [C++ Tracer] [CI] Remove DD_CI_VIS_API_KEY secret

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-08-20 11:34:32

Comparing candidate commit f9fa899 in PR branch xlamorlette/remove-dd-ci-vis-api-key with baseline commit 765983d in branch main.

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

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

• 🟩 = significantly better candidate vs. baseline
• 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

[zacharycmontoya]

The @AGENTS.md is needed rather than AGENTS.md so Claude can in-line the contents of the AGENTS.md file. What you have might work, but the @ is the best practice for inlining

Suggested change

	@AGENTS.md

[zacharycmontoya]

LGTM