Skip to content

fix(recipe): accept capture=video and websocket for browser-actions - #2557

Merged
chubes4 merged 1 commit into
mainfrom
fix/recipe-capture-video
Oct 2, 2026
Merged

chubes4 merged 1 commit into
mainfrom
fix/recipe-capture-video

Conversation

@chubes4

@chubes4 chubes4 commented Oct 2, 2026

Copy link
Copy Markdown
Collaborator

Fixes #2556.

The browser-actions runner accepts video and websocket captures, but the registry's browserActionCaptureValues omitted them. Every recipe step recording video failed recipe validate with wordpress.browser-actions capture does not support: video, so #2549–#2551 only worked through run, never through recipes. This was found rendering an extrachill-network journey demo on the network rig.

  • Adds video and websocket to browserActionCaptureValues.
  • New assertion in tests/recipe-validation-descriptors.test.ts: a recipe step with every runner-accepted capture yields no invalid-capture issue. It fails without the registry change (verified against a rebuilt core) and passes with it.
  • npm run build is clean, and the journey demo recipe now validates without the capture error.

AI-assisted: authored by Extra Chill Bot.

@chubes4
chubes4 merged commit f770b79 into main Oct 2, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

recipe validation rejects capture=video (and websocket) for wordpress.browser-actions

1 participant