Testing and conformance

Minimum integration tests

Test the host integration with synthetic data before connecting a real provider:

1. unambiguous grounding and authorization;
2. ambiguous candidates and clarification;
3. authorization denial before dispatch;
4. provider rejection and precondition failure;
5. acknowledgment followed by PRESENT;
6. acknowledgment followed by ABSENT_FINAL;
7. response loss and UNKNOWN;
8. verifier indeterminate or unavailable;
9. verifier-only reconciliation with zero redispatch;
10. wrong-tenant and stale-context rejection.

Assert dispatch count, physical mutation count, verifier reads, result, identities, and claim permission. Do not infer correctness from a provider response alone.

Conformance boundary

The Adapter Kit and conformance runner are offline evidence tooling. They can exercise bounded provider/verifier seams, hostile inputs, lifecycle counters, privacy rules, and closed result expectations. They do not certify a live provider, persistence layer, restart safety, production readiness, or package availability.

External-consumer validation must use the exact approved package artifact or authorized release channel, package-root imports, a clean consumer, and synthetic data. The portal currently publishes the declaration/API surface but does not claim that public package installation is open.