ddev/ai: replace agent YAML block with Markdown front matter files

[lucia-sb]

What does this PR do?

Replaces the two-part agent configuration (an agents: block in flow.yaml plus a separate prompts/{name}.md system-prompt file) with self-contained Markdown files that use YAML front matter for config and a plain-text body for the prompt.

Two file types are introduced:

• agents/{name}.md — front matter holds agent config (provider, model, max_tokens, tools); the body is the system prompt.
• prompts/{name}.md — type: prompt for task prompts, type: goal for goal verification text. Tasks reference them by name via prompt_ref / goal_ref.

FlowConfig.from_yaml() scans both directories eagerly, validates all cross-references, and surfaces agents, prompts, and goals dictionaries to the runtime. ResourceProvider gains prompt(name) and goal(name) methods. render_prompt() (path-based) is removed; everything uses render_inline().

Motivation

Having agent config split across flow.yaml and a loose .md file made it awkward to move or rename an agent. A single self-contained .md file per agent keeps all its configuration co-located, is easier to read, and aligns with how prompt files already work.

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add qa/required if this PR needs QA validation, or qa/skip-qa if it does not. Exactly one of the two is required.
• 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-prod-us1-5]

   

✨ Fix all issues with BitsAI

⚠️ Warnings

🚦 7 Pipeline jobs failed

PR | test / test (linux, ubuntu-22.04, ddev, ddev on Linux) / ddev on Linux     

PR | test / test (windows, windows-2022, ddev, ddev on Windows) / ddev on Windows     

PR | test / test-minimum-base-package (linux, ubuntu-22.04, ddev, ddev on Linux) / minimum-base-package-ddev on Linux     

View all 7 failed jobs.

ℹ️ Info

No other issues found (see more)

🧪 All tests passed
❄️ No new flaky tests detected

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

Useful? React with 👍 / 👎

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

[dd-octo-sts]

Validation Report

All 21 validations passed.

Show details

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and code coverage 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	✅
qa-label	Validate the pull request declares whether it needs QA for the next Agent release	✅
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