Refine AGENTS.md

[PerfectSlayer]

What Does This Do

This PR refines the AGENTS.md to avoid porting modules that are not supported yet by JUnit testing.

Motivation

Avoid trying to port modules to JUnit where the related features are missing. This tends to create a good amont of code that we will have a hard time to migrate later. Whereas if it uses Spock, we could migrate with the same tools and process than the original codebase migration.

Additional Notes

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.96 s	14.01 s	[-1.1%; +0.3%] (no difference)
startup:insecure-bank:tracing:Agent	13.02 s	13.02 s	[-0.7%; +0.6%] (no difference)
startup:petclinic:appsec:Agent	16.85 s	16.67 s	[+0.2%; +1.9%] (maybe worse)
startup:petclinic:iast:Agent	16.89 s	16.40 s	[-1.5%; +7.4%] (no difference)
startup:petclinic:profiling:Agent	16.80 s	16.87 s	[-1.5%; +0.6%] (no difference)
startup:petclinic:sca:Agent	16.93 s	16.76 s	[-0.3%; +2.3%] (no difference)
startup:petclinic:tracing:Agent	16.04 s	15.91 s	[-0.3%; +1.9%] (no difference)

Commit: 09a4a7f5 · 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-07-06 04:51:09 UTC ℹ️ Start processing command /merge

---

2026-07-06 04:51:14 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-07-06 06:51:48 UTC ❌ MergeQueue: The build pipeline has timeout

The merge request has been interrupted because the build 8271307645189534932 took longer than expected. The current limit for the base branch 'master' is 120 minutes.

Possible reasons:

• some mandatory checkruns are failing:
  • Check pull request labels
  • Check pull requests
  • Enforce Groovy migration

[PerfectSlayer]

/merge -f --reason "update agents markdown. unblocking merge from CI incident"

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-07-07 14:27:23 UTC ℹ️ Start processing command /merge -f --reason "update agents markdown. unblocking merge from CI incident"

---

2026-07-07 14:27:28 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 0s (p90).

---

2026-07-07 14:27:38 UTC ℹ️ MergeQueue: This merge request was merged

Warning

This change was merged without running any pre merge CI checks

Reason: update agents markdown. unblocking merge from CI incident