Page Health scanner ignores UVE mode, language, persona, variant and Time Machine — always scans published page

Problem Statement

The UVE Page Health a11y/GEO scanner always scans the published page, ignoring the current mode (edit/preview/live). Users need to scan drafts before publishing to catch compliance issues early — a primary documented benefit of the feature.

Only the page path (sanitizeURL) and host_id are sent to the scanner. The other page-resolving params — mode, language_id, persona, variantName, publishDate (Future Time Machine) — are dropped, so dotCMS re-resolves against defaults.

Impact: anyone scanning drafts, non-default languages/personas/variants, or future-dated pages. Front-end (UVE).

Steps to Reproduce

1. Open a page in the UVE in Edit or Preview mode and make an unpublished change that introduces an a11y issue.
2. Run the Page Health a11y (or GEO) scan from the page tools panel.
3. Observe the scan reports against the published page, not the draft.
4. Same gap applies when a non-default Language, Persona, Variant, or a Future Time Machine date is selected — none of those are reflected in what gets scanned.

Acceptance Criteria

• The scanned URL includes mode so draft/preview pages are scanned in the correct state.
• The scanned URL includes language_id, persona, and variantName matching the editor selection.
• The scanned URL includes publishDate so Future Time Machine state is scanned.
• host_id continues to be sent for multisite (existing behavior, #36162).
• Editor-fetch-only params (clientHost, depth) are not leaked to the public scanner.

dotCMS Version

Latest from main branch

Severity

High - Major functionality broken

Links

• Slack thread (#product) discussion with Marc Boutillette
• Related: #36162 / #36163 (host_id multisite fix)
• NA Freshdesk