# Topic naming baseline — pre-existing violations suppressed during initial enforcement rollout.
# All topics listed here were present in merged contracts before the producer-segment
# allowlist check was introduced. Fix these violations in separate follow-up work.
# Do NOT add new topics here — new violations are BLOCKED.
#
# Format: one topic string per line. Lines starting with '#' are ignored.

# TODO: build-loop producer should be omnimarket
onex.evt.build-loop.dod-checked.v1

# TODO: deploy producer should be omnibase-infra
onex.evt.deploy.rebuild-completed.v1
onex.cmd.deploy.rebuild-requested.v1

# TODO: savings/model-router/baselines producers should be omnimarket
onex.evt.savings.estimation-completed.v1
onex.evt.model-router.routing-decision.v1
onex.evt.baselines.computation-completed.v1

# OMN-16930: onex.tenant.events is the control-plane tenant-lifecycle topic
# OWNED BY onex-api (omninode_infra/docker/onex-api/topic_constants.py
# TENANT_EVENTS_TOPIC), not by omnimarket. node_projection_tenant_registry is a
# CONSUMER of it. Renaming it to satisfy this lint would require a coordinated
# producer change in a different repo plus an MSK topic migration, and the
# producer is the durable outbox OMN-16027 built precisely so tenant lifecycle
# events stop being lost -- churning its topic name is the last thing that
# surface needs. Baselined as a consumed foreign topic, not as debt this repo
# can pay down unilaterally.
onex.tenant.events
