feat(runner): perform a sequence of actions in one request with runner actions

[Goran Gajic (gorangajic)]

Relates to WIZ-12132. Depends on @qawolf/api-contracts 0.61.0, which ships with qawolf/platform#33491.

Overview of Changes

An agent that already knows its next few steps had to send each one as its own qawolf runner act call, a full round trip per step. qawolf runner actions takes a JSON array of up to ten of the same actions and performs them in one request, so the agent looks at the screen once, at the end. The answer reports each action as performed, not performed, or unknown when the runner stopped answering and the action may have landed, and says where the sequence stopped and why. --screenshot saves a frame after the last action, --screenshot-mode each saves one per action, and --continue-on-failure carries on past an action that did not take effect.

Testing

Ran end to end against the platform PR's preview with a real playwright runner: a four-action batch with a final frame, a two-action batch with a frame per step, a batch spanning a navigation, and a batch whose first step was a navigation the runner could not confirm. Frames and per-step results matched the screen.

bun run typecheck
bun run lint
bun run format:check
bun run knip
bun run test
bun run build

Three run.create tests fail on main as well (a workspaceId drift unrelated to this change).

To Do

• Bump @qawolf/api-contracts to 0.61.0 once it is published; typecheck fails against the current pin until then.

Checklist

• Changes follow the code style of this project
• Self-review completed
• Tests added/updated (or not applicable)
• No breaking changes (or described below)

🤖 Generated with Claude Code

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

_{Comment @coderabbitai help to get the list of available commands.}