Design System Audit: Meridian

Problem/Feature Description

The Meridian design system team has been operating for two years and recently hit a wall: product teams are reporting that components break silently during dark-mode updates, Figma and code are drifting apart, and it is becoming unclear whether any of the system's 47 components are actually being used correctly in production. The team lead has been asked by the VP of Engineering to produce a formal, evidence-based audit of the system before committing to a v3 roadmap. The goal is to understand where the system is mature and where it is failing — with clear, actionable findings the team can prioritize.

A summary document describing the current state of Meridian is provided at inputs/meridian-design-system.md. This document reflects what is available for review. There are no additional artifacts, analytics exports, or Figma access provided beyond this document.

Output Specification

Produce a complete audit report named audit-report.md. The report should give the team a rigorous, evidence-grounded picture of system health across all relevant domains. Prioritize findings that block safe adoption or create immediate risk, and group recommendations so the team can sequence their remediation work effectively.

Also produce a scorecard.md file that presents the maturity scores for each domain in a simple, readable table format that the team can share with stakeholders.