Add ddev validate to ddev tools

[luisorofino]

What does this PR do?

Adds a new DdevValidateTool shell tool to the AI agent harness at ddev/src/ddev/ai/tools/shell/ddev/validate.py. The tool wraps ddev validate with four subcommands:

• config — validates assets/configuration/spec.yaml against data/conf.yaml.example.
• models — validates spec.yaml against datadog_checks/<integration>/config_models/.
• metadata — validates metadata.csv.
• all — runs all ~20 validators in parallel. Intended as a final sweep, since it takes considerably longer than the targeted three.

A sync boolean maps to --sync for the targeted subcommands and to --fix for all.

Tests covering all subcommand shapes are in ddev/tests/ai/tools/shell/ddev/test_ddev_tools.py.

Motivation

The AI agent harness could edit assets/configuration/spec.yaml but had no way to subsequently run ddev validate config --sync or ddev validate models --sync to regenerate the derived files (conf.yaml.example, config_models/) from the updated spec. Without this tool, an agent that edits the spec produces an integration with stale generated files, causing CI to reject the PR.

The all subcommand additionally lets the agent run a final pre-commit sweep covering validators the targeted three do not (license headers, imports, readmes, codeowners, etc.).

DdevValidateTool closes this gap and completes the integration authoring lifecycle that the shell tools layer exposes to the agent.

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
• If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

[datadog-official]

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 87.60%

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: b288a9b | Docs | Datadog PR Page | Give us feedback!}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (loa/openmetrics-ai-gen@cf0749e). Learn more about missing BASE report.

Additional details and impacted files

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[dd-octo-sts]

Validation Report

All 20 validations passed.

Show details

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and Codecov settings	✅
codeowners	Validate every integration has a CODEOWNERS entry	✅
config	Validate default configuration files against spec.yaml	✅
dep	Verify dependency pins are consistent and Agent-compatible	✅
http	Validate integrations use the HTTP wrapper correctly	✅
imports	Validate check imports do not use deprecated modules	✅
integration-style	Validate check code style conventions	✅
jmx-metrics	Validate JMX metrics definition files and config	✅
labeler	Validate PR labeler config matches integration directories	✅
legacy-signature	Validate no integration uses the legacy Agent check signature	✅
license-headers	Validate Python files have proper license headers	✅
licenses	Validate third-party license attribution list	✅
metadata	Validate metadata.csv metric definitions	✅
models	Validate configuration data models match spec.yaml	✅
openmetrics	Validate OpenMetrics integrations disable the metric limit	✅
package	Validate Python package metadata and naming	✅
readmes	Validate README files have required sections	✅
saved-views	Validate saved view JSON file structure and fields	✅
version	Validate version consistency between package and changelog	✅

View full run