Certification & registry

import { certify } from "@trustysweep/connector-sdk";
const report = await certify(adapter, ctx, { writeProbe: true });

Checks: contract version; capability matrix schema; capability ↔ method correspondence; no permanent delete; quota validity; list pagination terminates and objects validate (no duplicates across pages); delta marker round-trip; fetch streams; write → fetch byte round-trip (opt-in probe on a scratch location); trash reversibility documented.

Registry states

State	Meaning
TRUSTY_BUILT	first-party connector
TRUSTY_VERIFIED	third-party code reviewed and certified by Trusty Sweep
THIRD_PARTY_VERIFIED	certified by the publisher’s harness run; reviewed for security
PRIVATE	usable only by the publishing application
DISABLED	removed from production

Only TRUSTY_BUILT, TRUSTY_VERIFIED and THIRD_PARTY_VERIFIED connectors may receive production credentials. Unreviewed third-party code never gains tenant or credential access.

Submission

1. Implement the adapter in a public repository with a ConnectorManifest (id, provider, capabilities, entry).
2. Run certify() against the simulated context and attach the report (its SHA-256 goes into the manifest).
3. Open a submission in the developer console (Connectors → Submit). Software checks run first (schema, harness report, dependency licenses, no network calls outside the declared provider hosts); a human review follows for production certification.
4. Certified connectors are listed at GET /v1/providers with their registry state.