https://redhat-internal.slack.com/archives/C0848GAELH3/p1764249630947139

Drops are currently being linked to artifacts based solely on matching commit SHAs. The linking logic in link_drops_to_artifacts() and link_artifacts_to_drops() does not enforce product boundaries or artifact type constraints. As a result, artifacts from other products (e.g., base-images) that share the same commit value end up being associated with drops where they do not belong, leading to cases where a rhaiis drop incorrectly contains artifacts from unrelated product lines.

This behavior incorrectly pollutes drop membership and causes misleading UI groupings and metrics in the Dashboard.

https://docs.google.com/document/d/1-cMmpWAb67Zx0R50nSPbfY81EdH5J_5IF9kCOzUC5Xc

Acceptance Criteria

• Drop linking is restricted to artifacts belonging to the same product.

• Only ArtifactType.CONTAINERS artifacts are linked to drops.

• Running the collector no longer adds base-images artifacts to rhaiis drops.

• Existing incorrect associations can be automatically cleaned or a script is provided to remove them.

• Unit / integration tests are updated to ensure cross-product contamination cannot occur when linking.