An adapter code deployment is not a valid turn-quality boundary

A merged or deployed adapter is not a valid production quality boundary unless traffic was actually routed through it. Establish exposure with the successful deployment matching the source revision, the runtime adapter flag, a positive traffic target, and preferably call-level route or model evidence. With weighted routing, compare adapter-tagged calls by their per-call path rather than treating every post-deployment call as exposed.