Anchor eval trial-signup metadata

This commit is contained in:
rcourtman 2026-04-10 19:02:35 +01:00
parent 8610f3b808
commit b929321a3d
5 changed files with 32 additions and 3 deletions

View file

@ -463,7 +463,11 @@ rate limited. The reused-instance browser-proof entry in
`POST /api/license/trial/start`, `409 trial_signup_required`, `429
trial_rate_limited`, and `Retry-After`, so the shared trial-start docs guard
can auto-discover that README alongside the rest of the governed trial-start
surface instead of relying on README-only fallback checks.
surface instead of relying on README-only fallback checks. The eval-pack
metadata in `tests/integration/evals/scenarios.json` must carry those same
anchors for the `trial-signup` scenario description, so deterministic and
agentic trial runs inherit the same canonical contract wording instead of
teaching a drifted summary path.
Playwright-driven public/commercial specs that support scenario-specific
endpoint overrides such as `PULSE_CLOUD_BASE_URL` or
`PULSE_COMMERCIAL_BASE_URL` must layer those values through that same shared