[Docs][13.3] Integrations: missing conceptual documentation for 3 new APIs/behaviors

Aspire 13.3 — Integrations conceptual docs gap

This issue tracks 3 Integrations changes shipped in Aspire 13.3 that introduce new APIs, behaviors, or user-visible surfaces with no conceptual documentation in microsoft/aspire.dev. This issue is scoped to the missing conceptual docs only — the What's New release-notes entries are being handled separately.

Source: 13.3 Change log wiki. Audit performed against release/13.3.

The Owner column is the author of the source PR (or first-write-access author if multiple); contributor-only rows are unowned and need to be picked up by the team. Use the Progress checklist below the table to mark items done — GitHub doesn't render checkable checkboxes inside table cells, so the checklist is separate.

Items needing docs

Progress checklist

• 1. Azure AI Foundry Prompt Agent support — @tommasodotNET
• 2. RabbitMQ v7 publisher and subscriber tracing
• 3. New AI models added to Foundry integration (GPT-5.4, Qwen3 VL) #845 — @sebastienros

Per-item rationale and content guidance

1. Azure AI Foundry Prompt Agent support

• Type: feature
• Source PR(s): #16353
• Where to add docs: integrations/cloud/azure/azure-ai-foundry/
• Why it needs docs / what to cover: Foundry Prompt Agent is only mentioned in 13-2 What's New (as removed). The new working AddPromptAgent in 13.3 has no docs. Need conceptual page or integration section + What's New entry.

2. RabbitMQ v7 publisher and subscriber tracing

• Type: improvement
• Source PR(s): #15659
• Where to add docs: integrations/messaging/rabbitmq-integration.mdx
• Why it needs docs / what to cover: RabbitMQ v7 publisher/subscriber tracing — extend integration page.

3. New AI models added to Foundry integration (GPT-5.4, Qwen3 VL)

• Type: improvement
• Source PR(s): #15210
• Where to add docs: integrations/cloud/azure/azure-ai-foundry/
• Why it needs docs / what to cover: New AI models in Foundry catalog (GPT-5.4, Qwen3 VL) — should be added to Foundry models docs.

This issue was generated from a structured audit of the 13.3 changelog against the release/13.3 branch of aspire.dev.