rhdh-release

name	rhdh-release
description	Manages RHDH releases — dates, status tracking, team coordination, freeze announcements, blocker bugs, CVEs, and release notes. Trigger on "release dates", "release status", "feature freeze", "code freeze", "blocker bugs", "CVEs", "release notes", "team breakdown", or any RHDH release management question.
compatibility	acli on PATH. Python 3 + gog CLI for Google Sheets/Docs.

<essential_principles>

Use `"Team[Team]" = "{{CLOUD_ID}}"` in JQL to filter by team. Cloud IDs are in the RHDH Team Mapping spreadsheet (column "Cloud ID"). Use the `open_issues_by_team`, `feature_freeze_issues_by_team`, or `code_freeze_issues_by_team` JQL templates. This is fast and does not require `parse_issues.py --enrich`. Include Jira search links for traceability in all outputs. Build links by URL-encoding the JQL: `https://issues.redhat.com/issues/?jql=`. Always wrap Slack messages in triple-backtick code blocks (` ```slack `) for easy copy-paste. Tell the user they can copy-paste this directly into Slack. When analyzing release health, check these risk indicators: 1. Blocker bugs near freeze dates — query with `priority = Blocker` 2. High open issue count per team — use team breakdown to identify overloaded teams 3. Missing release notes — query issues with empty Release Note Type 4. Critical CVEs — query vulnerabilities with CVE in summary 5. EPICs not in Dev Complete — check epic status

Always provide: specific issue counts with Jira links, team-level breakdown if applicable, actionable recommendations (retriage, escalate, extend timeline), and impact assessment.

For team coordination: 1. Retrieve team info from Google Sheets to get leads and Slack handles 2. Include team leads' Slack handles in all team communications 3. Provide Jira links scoped to each team's issues 4. Highlight teams at risk (high open counts, blockers) 5. Suggest follow-up actions per team Never read `.jira-token` into context. Always use shell substitution: `"$(cat "$TOKEN_FILE")"`.