Clean up AI generated code

[PerfectSlayer]

What Does This Do

Clean up AI generated code...

Motivation

Many details were lost. Intention were lost. Code got bloated on some parts.

Additional Notes

I expect to spend few days to fix core parts. Feel free to approve it whenever you find time because I will keep adding more and more fixes.
At some point, we would need to through AI at those fixes so they can get memory of their mistake.

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]

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6ead62416e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[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.89 s	13.86 s	[-0.8%; +1.2%] (no difference)
startup:insecure-bank:tracing:Agent	12.83 s	12.96 s	[-2.4%; +0.4%] (no difference)
startup:petclinic:appsec:Agent	15.61 s	16.26 s	[-12.5%; +4.4%] (unstable)
startup:petclinic:iast:Agent	16.44 s	16.56 s	[-2.3%; +0.8%] (no difference)
startup:petclinic:profiling:Agent	16.55 s	16.40 s	[-0.3%; +2.1%] (no difference)
startup:petclinic:tracing:Agent	15.69 s	14.96 s	[-3.6%; +13.4%] (unstable)

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

[PerfectSlayer]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-06-05 10:59:55 UTC ℹ️ Start processing command /merge

---

2026-06-05 11:00:02 UTC ℹ️ MergeQueue: waiting for PR to be ready

This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
It will be added to the queue as soon as checks pass and/or get approvals. View in MergeQueue UI.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

---

2026-06-05 12:23:06 UTC ℹ️ MergeQueue: merge request added to the queue

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

---

2026-06-05 13:40:03 UTC ℹ️ MergeQueue: This merge request was merged