Drop stale ddprof ThreadContext/BufferWriter* native-image references

[rkennke]

What

Removes the com.datadoghq.profiler.ThreadContext, BufferWriter, BufferWriter8, and BufferWriter9 entries from the GraalVM native-image -H:ClassInitialization config and reflect-config.json.

Why

DataDog/java-profiler#696 (Phase 3 of the OTEP context-storage migration) deletes all four classes from ddprof. This repo's ddprof dependency is currently pinned at 1.48.0 (predates that PR), so nothing is broken yet — but once it bumps to a release containing #696, a native-image build will fail: GraalVM errors when a class named in -H:ClassInitialization=...:run_time or reflect-config.json can't be resolved on the classpath.

ContextSetter is unaffected — java-profiler is restoring a minimal pure-Java offsetOf()/size() version of it for DatadogProfiler's continued use, so no change needed here for that.

Test plan

• reflect-config.json re-validated as well-formed JSON after edit
• CI native-image build (unaffected today since ddprof is still 1.48.0; this is a preemptive fix for the next bump)

🤖 Generated with Claude Code

[datadog-datadog-prod-us1-2]

More details

The native-image metadata removals are behaviorally consistent: the four deleted profiler classes no longer appear in either runtime class-initialization arguments or reflection configuration, while the remaining configuration stays valid. Gradle tests could not run because the sandbox could not download Gradle 9.6.1, but executable JSON and diff-level adversarial checks passed.

Was this helpful? React 👍 or 👎

_{📊 Validated against 5 scenarios · Open Bits AI session}

_{🤖 Datadog Autotest · Commit 438e61c · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}

[dd-octo-sts]

Hi! 👋 Thanks for your pull request! 🎉

To help us review it, please make sure to:

• Add at least one type, and one component or instrumentation label to the pull request

If you need help, please check our contributing guidelines.

[datadog-datadog-prod-us1-2]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 61.92% (+4.10%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: fda99b6 | Docs | Datadog PR Page | Give us feedback!}

[PerfectSlayer]

Thanks for the clean up

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	13.93 s	13.95 s	[-0.9%; +0.6%] (no difference)
startup:insecure-bank:tracing:Agent	12.93 s	13.00 s	[-1.2%; +0.2%] (no difference)
startup:petclinic:appsec:Agent	16.83 s	16.73 s	[-0.3%; +1.6%] (no difference)
startup:petclinic:iast:Agent	15.77 s	16.84 s	[-12.0%; -0.7%] (unstable)
startup:petclinic:profiling:Agent	16.83 s	16.40 s	[-1.9%; +7.2%] (no difference)
startup:petclinic:sca:Agent	16.84 s	16.72 s	[-0.0%; +1.5%] (no difference)
startup:petclinic:tracing:Agent	16.07 s	16.02 s	[-0.6%; +1.2%] (no difference)

Commit:fda99b64 · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-07-29 12:20:52 UTC ℹ️ Start processing command /merge

---

2026-07-29 12:20:56 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 1h (p90).

---

2026-07-29 13:08:57 UTC ℹ️ MergeQueue: This merge request was merged