Turn adapter registration into an explicit rollout gate

Adapter registration should be treated like a production change, not a convenience step.

Teams often talk about adding a new adapter as if it were harmless plumbing. In practice, adapter registration changes what the orchestration layer can call, route, and trust.

That makes registration a rollout gate. Before an adapter is accepted, the team should know what resources it can touch, how it fails, and what evidence exists when it misbehaves.

Minimum checks before registration

• Confirm the adapter's real capability surface, not just the happy path.
• Verify that deny paths are explicit when resources or scopes are missing.
• Make sure the rollback path is documented before traffic is routed.

If those checks are missing, the adapter is not integrated. It is merely present.