pikopod agent conformance

pikopod agent conformance <upstream> [--strict] [--handoff <path>]

Needs an imported spec for the upstream (a sandbox with the same name, or linked with --upstream) and recordings. Drift is baseline-relative; conformance is spec-relative.

Flag	Meaning
`--strict`	Exit 1 when any error-severity violation is found. The CI gate.
`--handoff <path>`	Also write the JSON report here, for `pikopod pr comment`.

examplepay — 37 JSON response(s) checked against the spec (2 skipped: non-JSON or no declared endpoint)
3 check(s) unverifiable: the sanitizer redacted the evidence — reported as neither pass nor violation

1 violation(s) — the provider disagrees with its own documentation:
  error   enum      GET /charges/{id} 200  /status                 value "disputed" not in documented set [pending, succeeded, failed] (4 occurrence(s))

these are SPEC-relative findings; `pikopod agent contract` shows what traffic has taught the sandbox instead

Without --strict the command exits 0 regardless of violations. Checks whose evidence the sanitizer redacted are never scored as passes. See Contract.

CLI

Interfaces

Schemas

pikopod agent conformance