lib.lssm-os-provider-conformance

LSSM OS provider conformance

Provider-neutral V0 contracts and a verifier-controlled offline qualification runner for implementations of ProviderExecutionPort from @lssm-tech/lib.lssm-os-runtime.

The runner owns an observable provider driver, separate mutation and read-only observation counters, credential-use recorder, failure and fencing injection, persistent restart store, and evidence trust verifier. Adapter factories receive only that driver—never a case ID—so a receipt cannot pass by describing an effect that the oracle did not observe.

import {
  expectedProviderQualificationTargetV0,
  runProviderConformanceV0,
  verifyProviderQualificationReceiptV0,
} from "@lssm-tech/lib.lssm-os-provider-conformance";

const target = {
  descriptor,
  fixture,
  identity,
  profile,
  createAdapter: async (driver) => new MyAdapter(driver),
};
const receipt = await runProviderConformanceV0(target);
const expected = expectedProviderQualificationTargetV0(target);
verifyProviderQualificationReceiptV0(receipt, expected);

driver.observe is the reconciliation boundary. It returns an exact, digest-bound present or absent state without changing effects, fences, or evidence. Current qualification requires stale-fence handling and restart replay to use this boundary. Calling driver.apply to rediscover prior state fails qualification even when the provider makes the second mutation idempotent. The method remains optional in the TypeScript interface so existing source continues to compile and receives explicit failed qualification evidence until migrated.

All ten cases are required. Limitations are descriptive and cannot waive scope effect isolation, exact credential-ref use, authoritative plan/effect digests, authorization and receipt attestations, exactly-once effects, exact stale-fence normalization, induced failures, trusted evidence, receipt tamper rejection, verified compensation, or read-only restart replay.

Canonical validation rejects undefined values, cycles, sparse arrays, non-finite numbers, functions, symbols, bigint, Date, Set, custom prototypes, dangerous property names, secret-bearing keys, and secret-shaped values. Qualification receipts bind the expected source revision, environment, profile, capabilities, fixture, driver protocol, case definitions, adapter artifact/package, results, and evidence. The case-registry digest includes the driver-protocol digest, so a legacy apply-only runner cannot restamp itself as current qualification.

This kit makes no live-provider, integration, SDK, or production qualification claim. Its output is evidence about the exact offline target identity supplied to the verifier.