Module conformance 

Provider conformance suite (04 §8).

Every provider implementation (FakeProvider included) must run all green before the CLI assembles it. This is the M0 minimal assertion set: four-way execute terminals, the reconcile fates (completed for archived succeeded and non-succeeded terminals — adopted verbatim, never demoted — plus neverDispatched / logUnavailable), fail-closed verdict caps plus a valid write, and cursor monotonicity — plus the callId-discipline and cancellation-discipline checks that need no fixture provisioning.

Fixture contract

run_conformance drives a live Provider, so the subject must be prepared (scripted fake, mock daemon, …) such that, in the session opened with ConformanceOptions::open, its first four execute calls settle succeeded, failed, cancelled, timedOut — in that order; when ConformanceOptions::dispatch_count is provided, a FIFTH execute must settle failed with retryable: true (the no-autonomous-retry group). The logUnavailable fate and the legal observation omission need faults the suite cannot cause through the SPI; subjects provide them via the option hooks (each check is recorded as skipped when its hook is absent).

Structs

CheckResult

Result of one conformance check.

ConformanceOptions

Options for run_conformance.

ConformanceReport

Report of a full conformance run.

Enums

CheckStatus

Outcome status of one conformance check.

Functions

run_conformance

Runs the conformance suite against provider (see the module docs for the fixture contract) and returns the per-check report.