Document method comment style

[mhlidd]

What Does This Do

Adds an agent code convention requiring concise Javadoc comments for class, method, and field documentation. The rule uses positive, active wording.

Motivation

Keeps declaration-level documentation discoverable through Java tooling and gives coding agents direct guidance without relying on negative phrasing.

Additional Notes

This is an instruction-only change with no runtime impact. The latest update addresses review feedback by replacing the previous never wording with an active instruction.

Validation:

• git diff --check
• Repository pre-commit checks, including Spotless and CodeNarc

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
• Update the CODEOWNERS file on source file addition, migration, or deletion — not applicable; no source files were added, migrated, or deleted
• Update public documentation with any new configuration flags or behaviors — not applicable; there are no runtime configuration or behavior changes
• Once approved, use merge queue to merge the PR

Jira ticket: N/A

[datadog-datadog-prod-us1]

More details

The new rule applies only to agent instructions. It does not change runtime code.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

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

[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	14.87 s	14.70 s	[+0.3%; +2.0%] (maybe worse)
startup:insecure-bank:tracing:Agent	13.63 s	13.70 s	[-1.4%; +0.4%] (no difference)
startup:petclinic:appsec:Agent	17.62 s	17.28 s	[+1.0%; +2.9%] (significantly worse)
startup:petclinic:iast:Agent	17.44 s	17.57 s	[-1.5%; +0.0%] (no difference)
startup:petclinic:profiling:Agent	17.44 s	17.49 s	[-1.3%; +0.7%] (no difference)
startup:petclinic:sca:Agent	17.52 s	17.47 s	[-0.8%; +1.5%] (no difference)
startup:petclinic:tracing:Agent	16.57 s	16.68 s	[-1.7%; +0.5%] (no difference)

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

[datadog-datadog-prod-us1]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 58.83% (-0.04%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 785c0d8 | Docs | View more details | Give us feedback!}

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-09-02 17:15:23 UTC ℹ️ Start processing command /merge

---

2026-09-02 17:15:31 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-09-02 17:29:59 UTC ❌ MergeQueue: The build pipeline contains failing jobs for this merge request

Build pipeline has failing jobs for 2c67cb3:

• check_smoke 4/4
• build_tests: [:smokeTest, smoke, -Xms256M -Xmx1024M]

⚠️ Do NOT retry failed jobs directly (why?).

What to do next?

• Investigate the failures and when ready, re-add your pull request to the queue!
• If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
• Any question, go check the FAQ.

Details

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected and the pipeline got canceled.

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-09-02 18:46:31 UTC ℹ️ Start processing command /merge

---

2026-09-02 18:46:36 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-09-02 19:37:57 UTC ℹ️ MergeQueue: This merge request was merged