Full page audit

Full audit of the current page — the one the scenario is on at this step. No parameters. Its main purpose is auditing the area behind authentication (account/dashboard): add the login steps, then «Full page audit». Only this single page is audited, no link crawling. In a test run the result is saved and appears in the «Audits» (cp/audit) list tagged «from scenario»; it collects accessibility (axe), load performance, SSL, broken links, meta/SEO, mobile layout and AI perception of the page (spends AI tokens). In preview/recorder the step runs in a lightweight check mode: it shows a short summary, saves nothing and spends no tokens. Lighthouse is not used.

Run a full audit of the current page — the one the scenario is on at this step. No parameters.

Why it exists: the regular site audit (by URL) cannot reach the area behind authentication — it does not log in. This step solves that: the scenario logs in first, then audits the already authenticated account page.

Only this single page is audited — no link crawling (safe for an account area: the bot will not click «Log out», «Delete», etc.). Need to audit several account pages — add several steps: navigate → audit → navigate → audit.

Run modes:

• Test run — full audit: accessibility (axe), load performance, SSL, broken links, meta/SEO, mobile layout and AI perception of the page. The result is saved and appears in the «Audits» section tagged «from scenario» with a link to the test. AI perception spends AI tokens.
• Preview / recorder — lightweight check mode: shows a short summary right in the recorder, saves nothing and spends no tokens (no AI perception).

Lighthouse is not used.

A typical sequence for auditing an account area:

1. Go to page — login page
2. Fill field — login and password
3. Click — Log in
4. Full page audit