authoring-web-scenarios

Navigate the browser to the starting page, optionally walk the flow once to confirm selectors, then call webmobai_generate_scenario to scaffold JSON from the live page. Review the draft, tighten selectors and assertions, and replay it with the webmobai-scenario CLI.

Use webmobai_generate_scenario_from_prompt with a plain-English description of the goal; it reads the current page state and returns schema-validated scenario JSON. This path requires WEBMOBAI_ANTHROPIC_API_KEY and degrades to a clean AI-disabled message without it.

Yes, set the top-level storageState field to a Playwright storageState file captured from a prior logged-in session instead of typing credentials in steps. The file holds live session cookies, so gitignore it and never inline its contents.

Version 1.4.0 requires an explicit success prefix from assertion, route, and visualSnapshot steps instead of treating any tool response as a pass. A route mock that never installed or an assertUrl with no matcher now correctly reports the failure it always was.

Neither generator emits storageState, saveStorageState, or pauseForManual, and the prompt-based path also drops route, viewport, browser, device, and continueOnFailure via its validation schema. Add these fields by hand during the mandatory review step.

No, pauseForManual is a no-op in headless mode: it logs a warning, records the step as pass, and continues immediately. Since webmobai-scenario and webmobai-suite launch hardcoded headless, capture MFA sessions through the interactive headed MCP flow instead.