@decocms/parity 0.12.0 → 0.13.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/AGENTS.md +3 -1
  2. package/CHANGELOG.md +13 -0
  3. package/dist/cli.js +4970 -4815
  4. package/package.json +2 -2
package/AGENTS.md CHANGED
@@ -38,7 +38,9 @@ Do **not** run parity for:
38
38
  - Have ONE URL and want to validate it works end-to-end? → `parity e2e` (functional validation)
39
39
  - Have ONE URL and only need absolute checks (vitals/console/SEO)? → `parity audit` (lighter, no flows)
40
40
 
41
- `parity e2e` reuses the same flows + checks as `parity run`, just in single-site mode (checks adapt with absolute criteria when one side is empty).
41
+ `parity e2e` reuses the same flows + checks as `parity run`, just in single-site mode (checks adapt with absolute criteria when one side is empty). It also does the same **selector automation** as `run` — platform detection, grounded LLM discovery + live-validation, and learning from each run — so you rarely need to hand-write `.parityrc.json` selectors (`--no-auto-selectors`/`--refresh-selectors`/`--no-learn` mirror `run`).
42
+
43
+ Do **not** fake single-site with `parity run --prod X --cand X` — it runs everything twice and reports a degenerate self-diff. `run` now rejects a missing `--prod` and points you at `parity e2e` (issue #141).
42
44
 
43
45
  ## Reading the JSON output
44
46
 
package/CHANGELOG.md CHANGED
@@ -7,6 +7,19 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
7
7
 
8
8
  ## [Unreleased]
9
9
 
10
+ ### Added
11
+
12
+ * **`parity e2e` now automates selectors like `parity run` (issue #141).** Single-site runs previously saw only `DEFAULT_SELECTORS` + hand-written `.parityrc.json` — `e2e` never detected the platform, never ran LLM selector discovery, and never learned from its flow runs (so `learned-selectors.json`, keyed by platform, never applied). It now detects the platform, runs the same grounded LLM discovery + live-validation pass, threads the platform into every flow, and promotes selectors learned from real successful interactions. New flags mirror `run`: `--no-auto-selectors`, `--refresh-selectors`, `--no-learn`. The discovery pass is now shared code (`src/engine/selector-discovery-pass.ts`) used by both commands.
13
+ * **Discovery covers the journey variant/quantity keys.** LLM selector discovery now infers `variantRow`, `quantityIncrement`, `quantityInput`, `sizeSwatch`, and `colorSwatch` (grounded on the real PDP and live-validated) — exactly the keys single-site users kept hand-writing in `.parityrc.json`.
14
+
15
+ ### Fixed
16
+
17
+ * **`purchase-journey-flow` now works in single-site mode.** The check was comparison-only: with no prod baseline it emitted a spurious "prod não produziu captura" issue per viewport instead of evaluating the journey. It now has a single-site branch (prod slot empty) that fails on a failed step or a skipped *critical* step, evaluating the checkout journey on its own terms — while still keeping the "cand crashed" critical signal for real prod↔cand comparisons.
18
+
19
+ ### Changed
20
+
21
+ * **`parity run` without `--prod` now points you at `parity e2e`.** `--prod` is no longer a hard `requiredOption`; omitting it exits with code 2 and a hint to use `parity e2e --url <cand>` for single-site validation, instead of forcing a wasteful `--prod X --cand X` self-comparison (issue #141).
22
+
10
23
  ## [0.12.0](https://github.com/decocms/parity/compare/v0.11.17...v0.12.0) (2026-07-27)
11
24
 
12
25
  ### Known issues