Phase 2: Automate Lighthouse Audits and Track Quality Metrics

[ckenst]

Overview

Automate Lighthouse audits during CI and record Performance, Accessibility, and SEO scores per version. This is the first step in the Quality Ledger initiative and aligns with the project vision to track quality metrics automatically.

Goals

• Run Lighthouse audits automatically during the CI/CD pipeline
• Record Performance, Accessibility, and SEO scores for each released version
• Store metrics in _data/quality_log.yml (or similar) with version, release date, commit SHA, and scores
• Make metrics available for future trend visualization and reporting

Implementation Notes

• Build and serve the site locally in CI so Lighthouse operates against repeatable output
• Collect a snapshot on release tags matching v*, with a manual trigger available for testing and recovery
• Store one entry per released version in a stable format for historical tracking
• Prevent a metrics-only commit from causing a deployment or versioning loop
• Refer to Phase 2 implementation strategy in ROADMAP.md for additional context

Related

• Depends on Phase 1.5 completion (Agent Readiness)
• Part of Phase 2: Quality Ledger & Metrics
• Related to: [Link Integrity Checker Issue #X]

Acceptance Criteria

• Lighthouse audit runs automatically on release tags
• Scores (Performance, Accessibility, SEO) are collected and persisted
• Manual trigger is available for testing and recovery
• Quality log format is stable and versioned
• CI/CD loop is not disrupted by metrics collection

Resources

• ROADMAP.md Phase 2: Quality Ledger & Metrics
• Lighthouse CI documentation