aiops: release-agents - Consolidate agent guidance #3880

AI Ops Summary

Consolidate release-agent and changelog-agent guidance while preserving unique instructions and their dependency.

Build Summary

Compare each legacy agent definition with its corresponding canonical definition. Resolve the inherited specification and agent-format conflicts before removing redundant files.

Linked Stories/Tasks/PRs/Epic

Parent: GIT-1293. Delivery: GitHub #3880, #3881. Related implementation: #1563 and #2653.

Milestones & Timeline

Consolidation precedes implementation only where its changes are a concrete prerequisite. No deadline or merge completion is asserted.

Problem / Opportunity

Parallel definitions risk losing unique guidance or preserving contradictory instructions. A checked issue checklist does not establish that the PR has merged.

Approach / Solution

Compare both release and changelog definition pairs, preserve unique content and the release-to-changelog dependency, and document each source file’s disposition. Resolve canonical-definition conflicts explicitly rather than assuming one format overrides adopted standards.

Use existing PR #3881; do not commit directly to develop or create a replacement PR. Keep implementation, workflow activation, version changes, tagging and deployment outside this consolidation.

Acceptance Criteria

Historical assertions preserved from the current issue—not independently verified:

• Both file pairs compared and differences resolved
• Unique guidance retained in each canonical definition
• Release-to-changelog dependency preserved
• Redundant legacy definitions removed
• Changes committed to develop, or any branch-protection blocker reported

Current review requirements:

• AI workflow/agent described
• Problem/opportunity scoped
• Success metric defined
• Documentation updated
• PR uses correct branch prefix (aiops/)
• PR description updated with relevant details
• Changelog entry prepared for PR (if applicable)
• Labels/types match org standards

Additional Context

Success means every source instruction has a reviewed disposition, required guidance survives, and applicable validation passes.

PR strategy: existing branch → develop; proposed PR title aiops: release-agents - Consolidate agent guidance; live AI Ops PR template. Verify PR labels separately: proposed type:aiops plus exactly one evidence-based changelog disposition. Preserve Zared’s issue ownership; verify PR assignment separately. This description change does not itself update PR metadata.

Stack subsequent implementation PRs only for a demonstrated dependency; record merge and retargeting order.

Definition of Ready (DoR)

• AI ops goal described
• Area/action mapped
• Acceptance criteria listed
• Estimate added

Definition of Done (DoD)

• All acceptance criteria met
• Solution/automation verified
• Documentation updated
• PR uses correct branch prefix (aiops/)
• PR uses the correct PR template based on type:aiops PR label or linked issue type or linked issue type:aiops label
• Branch deleted after merge
• Linked issue(s) updated with latest status and closed after merge
• The related epic should not be closed, instead updated with a comment to reflect the closed issue