adapter-conformance-check

Adapter conformance auditing detects leakage of per-adapter details into generic dispatchers, missing canonicalization before PrepareBody, hand-rolled error envelopes, and missing PassthroughRewrite wiring to prevent architectural drift.

Adapter conformance checking is an audit process enforcing provider-adapter integration contracts within a gateway dispatcher. You need it when adding or refactoring adapters to detect logic drift and validate canonicalization, error handling, and wiring.

Per-adapter logic leaks into the generic spec_adapter dispatcher when architectural contracts are violated during code changes. Auditing integration points and dispatch logic detects this drift, ensuring canonicalization and proper error handling are maintained.

To enforce canonicalization and error envelopes in provider adapters, apply a structured audit verifying proper data transformation before PrepareBody and validating standardized error handling to prevent hand-rolled envelopes.

Yes, the adapter conformance audit analyzes code paths under spec_* provider packages and the core dispatcher. It detects untouched prefix-lists without empirical evidence and validates existing wiring against architectural contracts.