Prepare issue templates for ASPIREPIPELINES001-003 diagnostics

[Copilot]

PR dotnet/aspire#12416 splits ASPIREPUBLISHERS001 into three sequential diagnostics. This PR prepares structured templates for creating the corresponding documentation issues.

Files Created

• proposed-diagnostic-issues/ASPIREPIPELINES{001,002,003}.md - Complete issue data matching the 06-diagnostic-addition.yml template fields:

  • 001: Pipeline infrastructure APIs (IPipelineActivityReporter, IReportingStep, IReportingTask, PublishingContext, etc.)
  • 002: Deployment state management APIs (IDeploymentStateManager, PublishingOptions.Deploy/ClearCache/Step)
  • 003: Container image building APIs (IResourceContainerImageBuilder, ContainerBuildOptions, Docker/Podman runtimes)

• proposed-diagnostic-issues/README.md - Issue creation instructions (manual form fill, gh CLI, API)

• proposed-diagnostic-issues/POST-CREATION-TASKS.md - Documentation updates needed post-issue creation (overview.md entries, aspirepublishers001.md obsolescence notice)

• DIAGNOSTIC-ISSUES-SUMMARY.md - Context and next steps

Usage

Copy field values from ASPIREPIPELINES{001,002,003}.md into the issue template form at https://github.com/dotnet/docs-aspire/issues/new?template=06-diagnostic-addition.yml

Context

Direct issue creation via GitHub API requires authentication not available in this environment. These templates provide all necessary information for manual or scripted issue creation.

Original prompt

Based on the new diagnostics introduced in dotnet/aspire#12416 open issues for each diagnostic based on the template in https://github.com/dotnet/docs-aspire/issues/new?template=06-diagnostic-addition.yml.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.