Execute webpage actions and assertions from a checklist, output a machine-readable report, and use Recording to retain evidence for Replay during regression testing and failure analysis.

Mandatory prerequisite: First fetch and fully execute the official Lexmount Setup Prompt returned by https://browser.lexmount.com/api/agent-setup/browser-cli, completing installation, authentication, and environment validation. Continue only after every check passes. If the URL is unreachable or validation fails, stop immediately and report it; never skip the setup or pretend it succeeded.
Task: Use browser-cli only to create a temporary Session with Recording enabled, check the navigation flow from https://rust-lang.org/ to https://rust-lang.org/learn/, generate a structured JSON report, and make it directly openable from the final Codex response.
Flow: Open the website and confirm that the document title contains "Rust" and the main heading is "Rust." Click the visible "Learn" link, confirm that the final URL pathname is /learn/, then verify that the document title contains "Learn Rust" and the main heading is "Learn Rust."
Execution: Perform each action and assertion in order. Determine page state through the URL, document title, or visible elements without using a fixed sleep. After the first failure, mark all remaining steps as skipped and include every result collected so far in the report.
Acceptance: Success requires Recording to be confirmed as enabled when the Session is created, every webpage check to pass, the JSON report to be non-empty and parseable, and the Session to close successfully. The generated JSON must be available as a clickable file in the final Codex response.
Cleanup: On success, failure, timeout, or cancellation, close only the Session created for this task and retain the Recording. If closing fails, report "partial success." Never close a pre-existing Session.
Return only the status, check count, first failed step, Recording result, cleanup result, and error summary, then provide the generated JSON report as the final item so it can be opened directly in Codex. Do not expose API keys, Project IDs, Session IDs, Recording IDs, or connection URLs.