Phase 2: Implement Broken Link Checker for Quality Ledger

[ckenst]

Overview

Implement a broken link checker (e.g., linkinator) to log broken link counts against the current version. This complements Lighthouse tracking and continues the quality metrics initiative.

Goals

• Integrate a broken link checker into the CI/CD pipeline
• Log broken link counts per released version
• Store metrics in _data/quality_log.yml (or similar) with version and broken link count
• Surface link integrity issues as part of the quality ledger

Implementation Notes

• Use a tool like linkinator or equivalent to scan for broken links
• Run link checks during release or tag workflow
• Collect a snapshot on release tags matching v*
• Store results in the same quality log format as Lighthouse metrics
• Append rather than overwrite records to maintain historical data
• 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
• Complements: [Lighthouse Tracking Issue #X]

Acceptance Criteria

• Broken link checker runs automatically on release tags
• Broken link count is collected and persisted
• Results are stored in the quality log with version information
• Manual trigger is available for testing and recovery
• Failed link checks are reported clearly in CI logs

Resources

• ROADMAP.md Phase 2: Quality Ledger & Metrics
• linkinator documentation: https://github.com/JustinBeckwith/linkinator