Check back with Lindsey on when we can move to backlog:

As a Swatch developer, I want to disable the legacy consumer and make the new Product kafka topic the sole source of product messages so that Swatch is fully migrated off the UMB topic.

Take a look at SWATCH-3458 for reference about how we executed this migration pattern previously

Acceptance Criteria:

• Disable and remove Swatch’s consumer for the legacy topic: VirtualTopic.services.productservice.Product
• Ensure Swatch only consumes from the new topic: TBD
• Validate:
  • No product data regressions post cutover
  • Observability dashboards show expected throughput
  • No increase in error rates or processing delays
• Remove any config flags or feature toggles used for dual-consumption logic
• Clean up:
  • Topic subscription metadata
  • Consumer queue configs for the legacy topic
  • Legacy-topic-specific logging or schema handling paths