Creating a destination entity does not prove an integration route exists

Creating a destination entity in an application does not prove an external identifier can route to it. When provider-to-internal routing is code-defined or stored separately, onboarding must verify both sides: the destination exists and the external code resolves to its exact stable identity. This applies to integrations with explicit mapping layers; it does not apply when the destination itself owns the external identifier as validated configuration.

Method: after adding an org/team/category, run one bounded mapping readback with the provider identifier and verify a representative ingest persists the destination ID. Surface unmapped identifiers as an actionable configuration error instead of silently creating an unassigned record.