Value Statement

Implement history support in OCM.io discovered policies to bridge the gap between framework-deployed and discovered policies.

Definition of Done for Engineering Story Owner (Checklist)

• The UI MUST be updated to retrieve and display the last 10 compliance events by querying the policy template resources (e.g., ConfigurationPolicy, CertificatePolicy, OperatorPolicy status), which now contain the event data.
• The existing policy history page MUST be moved and displayed as a new tab (e.g., "History" or "Event History") within the Policy details page.
• The existing "View history" link on the Policy details > Results page MUST be updated to link directly to the new "History" tab. 
• The new "History" tab MUST be available and correctly populated with event data for both policies deployed via the RHACM framework and policies deployed via alternative methods (Discovered Policies).
• UI must gracefully handle cases where no history events are present.

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.