Export the browser actions runner from the package entrypoint

[chubes4]

Summary

• re-export runBrowserActionsCommand, runBrowserScenarioCommand, and BrowserActionsRunPlan from the runtime-playground entrypoint

Why

The browser actions runner is the engine's declarative step executor: it takes browser interaction steps, drives them, and collects artifacts. It is currently reachable only by importing a source path inside the package, so a consumer that wants to run engine steps has to reimplement the driver instead — its own browser launch, its own interception, its own capture and artifact handling.

PlaywrightBrowserEnvironmentSession is already exported, and the runner accepts a caller-supplied session, so the missing export is the only thing preventing a consumer from supplying a prepared browser context and letting the engine execute the steps.

Verification

• tsc -b --force packages/runtime-core packages/runtime-playground packages/cli — clean
• the built entrypoint resolves the new exports:

runBrowserActionsCommand: function
runBrowserScenarioCommand: function
createPlaywrightBrowserEnvironmentContext: function

No behaviour changes; this only widens the public surface.

AI assistance

• AI assistance: Yes
• Model: OpenAI gpt-5.6-sol
• Tool: OpenCode
• Used for: Identifying the missing export while removing a duplicated browser driver in a consumer, and verifying the built entrypoint, under Chris Huber’s direction.