[EPIC] Contributor and Azure Service Onboarding

## Problem statement

Contributors and Azure service teams need a predictable path from initial request through design, implementation, validation, documentation, ownership, and release. Current onboarding requests and process improvements are spread across independent issues, which makes progress, blockers, and completion difficult to assess.

## Outcome

Contributors and Azure service teams can follow a clear, measurable onboarding path with appropriate automation, human ownership, and consistent completion criteria.

## In scope

- Intake and routing for new services, commands, and MCP servers
- Contributor setup, guidance, diagnostics, and implementation checklists
- Architecture, security, testing, documentation, ownership, and release readiness requirements
- Progress tracking, escalation, completion verification, and feedback for onboarding requests
- Automation that reduces repeatable onboarding coordination while preserving human decisions

## Out of scope

- Prioritizing the product value of service coverage after intake
- Implementing service commands outside their specific child workstream
- Packaging, distribution channels, or host compatibility
- General customer adoption and product-usage analysis

## Routing rules

- Each service or contributor onboarding request is a child until it is completed, declined, or moved to a dedicated implementation Epic.
- Process automation and contributor-experience work should use focused child Epics.
- Final ownership, architecture, security, and pull request approval remain human decisions.

## Success criteria

- [ ] Every onboarding request has complete intake, routing, and an accountable owner
- [ ] Each accepted request has a tailored implementation and validation checklist
- [ ] Contributors can diagnose prerequisites and common setup failures without waiting for manual help
- [ ] Stalled work has visible blockers and an escalation path
- [ ] Completion verifies implementation, tests, documentation, ownership, and release readiness

## Parent initiative

microsoft/mcp#3108