Summary

Currently, when a component's catalog-info.yaml is updated with new metadata (e.g., adding a Slack channel, updating an owner, or adding a repository tag), the associated Scorecard checks do not reflect these changes until a user manually navigates to the UI and triggers a "Rerun Checks" action. This proposal requests an automated trigger to re-evaluate scorecards whenever the underlying Catalog entity is updated.

The Problem

Stale Data: Scorecards often show "Failing" grades for checks that have actually been resolved in code, leading to a lack of trust in the dashboard.

Manual Overhead: Developers must remember to manually trigger a refresh, adding unnecessary steps to their workflow.

Delayed Feedback: There is a "lag" between fixing a metadata issue and seeing the visual confirmation of that fix.

Proposed Solution

Implement an event-driven refresh mechanism. The system should listen for lifecycle events from the Catalog (specifically EntityUpdated or CatalogUpdate) and automatically queue a scorecard re-scan for the affected entity.