Feature spec: deployments and release visibility

[CompN3rd]

Summary

Add deployment/release visibility for teams using Azure DevOps Releases or deployment stages.

Product rationale

Release Management can be valuable for enterprise ADO users, especially teams still using classic Release pipelines. The feature should be framed around developer-facing deployment status, not release administration. If most users rely on YAML pipelines, this may be better folded into a Pipelines/Deployments view instead of a separate Release view.

Proposed UX

Add either:

1. A Deployments view that unifies deployment stages from YAML pipelines and classic releases, or
2. A Releases view for classic Release pipelines only, if there is clear demand.

Display:

• Release/deployment name
• Environment/stage
• Status/result
• Artifact/build version
• Requested by
• Created/deployed time
• Approval state where applicable

Details panel:

• Environment history
• Stage/job status
• Approvers and approval state
• Artifact versions
• Links to deployment logs

Suggested actions

• Open release/deployment in browser
• Approve/reject deployment, if permitted and in scope
• Redeploy, if permitted
• View logs/artifacts

Integration with existing core features

• Link deployments back to work items and PRs where Azure DevOps provides traceability.
• Surface deployment status in PR/work item detail panels only when relevant.
• Reuse provider, webview, and scope patterns from existing views.

MVP scope

• Read-only deployment/release listing.
• Details panel with environment/stage status and browser links.
• No approval or redeploy actions until permissions and UX are proven.

Non-goals

• Full release definition editing.
• Environment/resource administration.
• Agent pool management.
• Replacing Azure DevOps release management UI.

Acceptance criteria

• The feature works read-only for users without release management permissions.
• Classic Release users can see recent releases and environment status.
• YAML deployment users are not forced into a classic-release-only view if the data is unavailable.
• npm run compile passes.
• npm run lint passes or reports only existing unrelated warnings.