Replace declarative release readiness states with actionable guidance

## Problem

During the Azure Key Vault team's first SDK release, the agent reported states like *".NET not ready for release"* without explaining what was blocked, who could unblock it, or what action to take. The team didn't know how to proceed and had to escalate through Teams.

Declarative status messages ("not ready") without next steps create dead ends that force human escalation.

**Source:** First-time service team feedback (Azure Key Vault)

## Proposed Solution

Replace opaque readiness states with structured, actionable output. Every blocked item should follow this pattern:

> ❌ **Blocked:** APIView approval missing for `Azure.Security.KeyVault.Keys` (.NET)
> 👉 **Action:** Request API review approval from the .NET SDK team
> 👤 **Suggested contacts:** {relevant SDK owner(s)}
> 🔗 **Link:** {direct APIView URL or relevant resource}

Specifically:
1. **What** is blocked — the specific requirement that is not met
2. **Who** can unblock it — named contacts or team aliases
3. **How** to proceed — the exact next action the user should take
4. **Where** to go — a direct link to the tool, page, or resource

## Acceptance Criteria

- [ ] No release readiness output contains a blocked item without a corresponding next step
- [ ] Blocked items include: blocker description, recommended action, suggested contact(s), and a link
- [ ] Contact suggestions are contextual (e.g., language-specific SDK owners for APIView approvals)
- [ ] Output is structured and scannable (not buried in prose)

## User Impact

Transforms the release readiness experience from "here's what's wrong" to "here's what to do." Eliminates dead-end messages that force service teams to escalate through side channels. Reduces time-to-release by making every blocker immediately actionable.

The issue does not name a file, test, or entry point. Start by locating the release-readiness output in this repository and trace how blocked items are assembled. Done means every blocked item has a blocker description, action, contextual contacts, and a direct link in a structured, scannable format.

Written by the indexing model from the issue text.