Add LLMObsContextTest

[mcculls]

Motivation

Meet expected test coverage.

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Add your completed PR to the merge queue by commenting /merge. You can also:
  • Customize the commit message associated with the merge with /merge --commit-message "..."
  • Remove your PR from the merge queue with /merge -c
  • Skip all merge queue checks with /merge -f --reason "reason"; please use this judiciously, as some checks do not run at the PR-level (note: the PR still needs to be mergeable, this will only skip the pre-merge build)
  • Get more information in this doc

Jira ticket: [PROJ-IDENT]

[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.99 s	14.00 s	[-0.9%; +0.8%] (no difference)
startup:insecure-bank:tracing:Agent	13.00 s	13.09 s	[-1.3%; -0.0%] (maybe better)
startup:petclinic:appsec:Agent	16.96 s	16.70 s	[+0.5%; +2.6%] (maybe worse)
startup:petclinic:iast:Agent	16.89 s	16.92 s	[-1.1%; +0.7%] (no difference)
startup:petclinic:profiling:Agent	16.82 s	16.81 s	[-0.7%; +0.9%] (no difference)
startup:petclinic:sca:Agent	16.25 s	16.74 s	[-7.5%; +1.6%] (no difference)
startup:petclinic:tracing:Agent	16.00 s	15.55 s	[-1.5%; +7.2%] (no difference)

Commit:fb276bab · 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.

[bric3]

I don't know much the context API, but looking the test looks ok to me.

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-06-29 23:45:54 UTC ℹ️ Start processing command /merge

---

2026-06-29 23:46:00 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-06-30 00:48:25 UTC ℹ️ MergeQueue: This merge request was merged