parity journey

parity journey runs only the purchase journey (home → PLP → PDP → shipping → cart → checkout) step-by-step on both sides. It skips the sitemap crawl and the LLM aggregation, so it's the cheapest CI loop for "is checkout still working?".

parity journey --prod https://old.com --cand https://new.dev \
  --cep 01310-100 --junit results.xml --github

Flag	What it does
`--cep`	CEP for the shipping-calculation step (default `01310-100`)
`--junit <file>`	Emit JUnit XML for CI test reporting
`--github`	Emit GitHub annotations + write `$GITHUB_STEP_SUMMARY`
`--json`	One-line JSON verdict to stdout
`--no-report`	Skip the HTML report (fastest)
`--accept-prod-quirks`	Don't fail on known prod-side quirks (e.g. VTEX seller-null)

Writes report.html / report.json plus the optional JUnit XML / GH annotations.

Use journey in the tight per-commit loop and a full parity run (or parity pr) for the deep audit.

See also