Files
open-design/e2e/ui
CaprikaandGitHub 2feaee4237 fix(web): validate onboarding runtime on Continue (#7164)
* fix(web): validate onboarding runtime on continue

* chore: ignore local pi state

* refactor(web): remove unused onboarding code

* test(e2e): align onboarding Continue expectations

* fix(web): discard onboarding validation results the user moved past

Continue awaits a validation round trip before it persists the runtime
configuration and finishes onboarding, but its closure is frozen at click
time and nothing rechecked the intent afterwards. Two ways that surfaced:

- Back stays enabled while the request is in flight. Clicking it returned
  the user to the model-source chooser, then the late success persisted the
  configuration they had just abandoned and completed onboarding under them.
- The inputs being validated stay editable. A success for a replaced BYOK
  key still completed onboarding against the click-time configuration.

`inputKey` already guarded what gets DISPLAYED — `visibleAgentTestState` and
`visibleProviderTestState` fall back to idle once it drifts. Apply the same
rule to what gets PERSISTED: `continueAttemptStillCurrent` requires the
attempt to still be on the runtime setup step, on the same runtime, and
against the inputs it validated, reading them from a ref the continuation
can actually ask.
2026-08-21 10:55:36 +00:00
..