ROX-36146: Add release ticket to advisory

[mtodor]

Description

This PR is adding release ticket to release advisory

Validation

• Checked Jira ticket ID is correct
• Compared format with ACS release Resource in release history

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited), Organization UI (inherited)

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: db52b059-83e5-49a7-bbcd-75b499d9551c

📥 Commits

Reviewing files that changed from the base of the PR and between eb2163c and 2f6f1b1.

📒 Files selected for processing (2)

• releases/0.2.0/agentic-cluster-security-suite-0-2--0-2-0--prod.yaml
• releases/0.2.0/agentic-cluster-security-suite-0-2--0-2-0--stage.yaml

---

📝 Walkthrough

Summary by CodeRabbit

• Bug Fixes

  • Resolved issue ROX-36146 in the production and staging release configurations.

• Documentation

  • Updated release notes with RHEA references for the release tag and quick-start documentation.
  • Standardized release metadata across production and staging release information.

Walkthrough

The production and stage release manifests now use RHEA references and record fixed issue ROX-36146. The previous synopsis, topic, description, and solution fields were removed.

Changes

Release note updates

Layer / File(s)	Summary
Update release note metadata releases/0.2.0/agentic-cluster-security-suite-0-2--0-2-0--prod.yaml, releases/0.2.0/agentic-cluster-security-suite-0-2--0-2-0--stage.yaml	Both manifests add two references and record fixed issue ROX-36146. The previous descriptive fields were removed.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: janisz

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the change to add release ticket ROX-36146 to the advisory.
Description check	✅ Passed	The description explains that the release ticket is added to the release advisory and states the validation performed.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch mtodor/ROX-36146-add-ticket-to-advisory

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

E2E Test Results

Commit: eb2163c
Workflow Run: View Details
Artifacts: Download test results & logs

=== Evaluation Summary ===

  ✓ cve-cluster-does-not-exist (assertions: 3/3)
  ✓ list-clusters (assertions: 3/3)
  ✓ cve-cluster-does-exist (assertions: 3/3)
  ✓ cve-detected-clusters (assertions: 3/3)
  ✓ cve-cluster-list (assertions: 3/3)
  ✓ cve-nonexistent (assertions: 3/3)
  ✓ cve-detected-workloads (assertions: 3/3)
  ✓ cve-log4shell (assertions: 3/3)
  ✓ cve-clusters-general (assertions: 3/3)
  ~ rhsa-not-supported (assertions: 1/2)
      - MaxToolCalls: Too many tool calls: expected <= 4, got 5
  ✓ cve-multiple (assertions: 3/3)

Tasks:      11/11 passed (100.00%)
Assertions: 31/32 passed (96.88%)
Tokens:     ~52482 (estimate - excludes system prompt & cache)
MCP schemas: ~12562 (included in token total)
Agent used tokens:
  Input:  8948 tokens
  Output: 20878 tokens
Judge used tokens:
  Input:  29277 tokens
  Output: 25604 tokens

[codecov-commenter]

❌ 2 Tests Failed:

Tests completed	Failed	Passed	Skipped
380	2	378	12

View the full list of 2 ❄️ flaky test(s)

::policy 1

Flake rate in main: 100.00% (Passed 0 times, Failed 110 times)

Stack Traces | 0s run time

- test violation 1
- test violation 2
- test violation 3

::policy 4

Flake rate in main: 100.00% (Passed 0 times, Failed 110 times)

Stack Traces | 0s run time

- testing multiple alert violation messages 1
- testing multiple alert violation messages 2
- testing multiple alert violation messages 3

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}