Module conformance 

bynk registry conformance (first-party registry track R0, #2311): run the registry protocol’s observable behaviour against a registry URL, and report each check.

Servers are judged by the client’s own code wherever it can be used — the config.json and key-chain reading, line verification, archive fetching and checksumming are exactly what a consumer runs. Only requests a client would never make (a bad token, a mismatched URL, a hostile archive, an oversized declared length) go through transport::request directly.

A full run publishes one throwaway package, <org>/conformance_<utc>_<hex>, and yanks every version it published: indexes are append-only, so that package stays behind, yanked, and the report names it (decision B). --read-only publishes nothing.

Structs

Check

One check’s result.

Options

What to run against.

Report

A run’s results.

Enums

Outcome

A check’s outcome.

Constants

FULL_RUN

Every check a full (publishing) run reports, in order, so the set of ids is stable whatever fails: a check a run couldn’t reach is reported skipped.

NONCONFORMANT

A failed check: the registry breaks the protocol.

Functions

run

Run the suite.