verify-page

Page-level regression checks run by identifying every section with an assertions file, looping per-section verification, and aggregating the results into a single consolidated report. This process scans template pages to detect regressions across all configured sections automatically.

The best way to verify pages without modifying code is to use a read-only regression tool that runs assertions and aggregates results without mutating code or triggering refinement. This ensures safe quality-assurance testing across template sections.

You generate exportable page run logs by executing a consolidated page report that aggregates per-section verification results. This report captures all regression assertions across the template page, providing an auditable log of the verification run.

Yes, section-level verification runs individually before aggregating page-level regression results. The tool discovers sections with assertions and executes per-section checks, then aggregates all individual section results into the final page report.

Page verification does not require assertions.json for every section. The tool discovers and verifies only the sections that have an assertions.json file, skipping sections without assertions during the page-level regression check.

Page regression verification avoids triggering code refinement to maintain a strictly read-only execution contract. This constraint ensures the quality-assurance process only reports regressions without altering the template codebase.