A repository retires legacy-release-agent and replaces it with release-coordinator-agent. The team wants to preserve auditability for historical runs while ensuring new release workflow requests use the replacement path. A reviewer checks the retired profile and the replacement workflow.

# .github/agents/legacy-release-agent.md
---
name: legacy-release-agent
description: RETIRED. Use release-coordinator-agent for new release tasks.
target: github-copilot
user-invocable: false
disable-model-invocation: true
tools: []
---

Retirement record:
- Replacement: release-coordinator-agent
- Retired on: 2026-05-20
- Do not delete historical issues, pull requests, workflow logs, or artifacts.
# .github/workflows/release-coordinator.yml
name: release-coordinator

on:
  workflow_dispatch:
    inputs:
      release_issue:
        description: GitHub issue number containing the approved release plan
        required: true

permissions:
  contents: read
  issues: read
  pull-requests: read
  actions: read

jobs:
  summarize:
    runs-on: ubuntu-latest
    steps:
      - name: Record release handoff
        run: |
           echo "Use release-coordinator-agent for new release work"
           echo "Legacy release-agent records remain available in prior issues and runs"
Evaluate the following statements.

1. The retired profile blocks both manual and inferred selection.
2. The workflow keeps a manual continuity path for new releases.
3. The configuration deletes historical audit evidence.