Adapter Capability Claims Should Be Probed, Not Presumed

What an adapter says it supports and what it actually does under denial, timeout, and conflict are different documents, and only probing reads the real one.

Every adapter arrives with claims. Production is where unprobed claims get tested by accident, at the worst possible moment, with real permissions attached.

Probes worth running first

• Deny a permitted-looking action and confirm the adapter surfaces it.
• Time out a dependency and observe what the adapter reports upstream.
• Issue conflicting writes and check the adapter’s ordering story.

Use the adapter system, integration guide, and examples to verify what the adapter actually does before it carries authority.