vrr/Pulse
2
0
Fork 0
mirror of https://github.com/rcourtman/Pulse.git synced 2026-05-04 06:20:14 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

Anchor trial retry-after UI proof

Browse source
This commit is contained in:
rcourtman 2026-04-10 23:58:54 +01:00
parent 0a4c84daaa
commit d92ce0c54b
6 changed files with 38 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

14
docs/release-control/v6/internal/subsystems/deployment-installability.md
View file

@ -463,11 +463,15 @@ 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. 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.
surface instead of relying on README-only fallback checks. That README must
also keep the named Pulse Pro browser proof,
`tests/58-self-hosted-trial-rate-limit-ui.spec.ts`, on the owned trial-start
surface so the user-facing retry-after proof does not drift into an orphaned
integration spec. 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