Cover documentation for config inversion json checks

[amarziali]

What Does This Do

Add documentation coverage for the configuration inversion json checks (claude + doc)

Motivation

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
  • 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: 5560757b1a

ℹ️ 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".

[amarziali]

@codex review

[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.01 s	14.01 s	[-1.2%; +1.3%] (no difference)
startup:insecure-bank:tracing:Agent	12.89 s	13.02 s	[-1.9%; +0.0%] (no difference)
startup:petclinic:appsec:Agent	16.58 s	16.51 s	[-1.4%; +2.2%] (no difference)
startup:petclinic:iast:Agent	16.54 s	16.59 s	[-1.8%; +1.2%] (no difference)
startup:petclinic:profiling:Agent	16.36 s	16.68 s	[-3.2%; -0.5%] (maybe better)
startup:petclinic:tracing:Agent	14.99 s	15.04 s	[-12.1%; +11.5%] (unstable)

Commit: 1812e7b8 · 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-06-01 12:52:48 UTC ℹ️ Start processing command /merge

---

2026-06-01 12:52:53 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-06-01 14:04:49 UTC ℹ️ MergeQueue: This merge request was merged