Connector SDK

@trustysweep/connector-sdk (Apache-2.0) defines the versioned Provider Adapter contract:

Method	Capability
quota(ctx)	quota
list(ctx, filter, cursor)	list (required)
delta(ctx, marker, cursor), currentMarker(ctx)	delta
fetch(ctx, id)	read
write(ctx, req)	write (makes the adapter a Destination Adapter)
trash(ctx, id, expectedVersion), untrash(ctx, id)	trash, restore
copy(...), move(...)	copy, move
authorizationUrl, exchangeCode, refresh, revoke	OAuth adapters

Adapters publish a capability matrix (read, write, list, delta, quota, metadata, permissions, trash, permanent_delete, restore, copy, move, external_destination, change_feed, known_lossiness, authorization, limits, quotaSemantics). Parity is never faked: the certification harness fails an adapter that claims a capability without implementing it, or implements one it does not declare. permanent_delete can never be implemented.

Adapters receive a scoped AdapterContext with a pre-authenticated fetch, never other connections, never the engine. Provider tokens stay inside Sweep’s connector boundary.

Reference connector: connectors/s3 (S3-compatible object storage with SigV4 in WebCrypto, multipart upload, hash verification, reversible trash prefix).