Launch-ready chart quality pass

Problem

The chart templates shipping at public launch have been built incrementally across milestones, and each carries accumulated inconsistencies — label positioning that varies between bar and line charts, grid line density that doesn't match the locked v1 visual language, color encodings that work differently in single-series vs. multi-series contexts, and SVG output that may be unnecessarily large for complex charts. A systematic quality pass is needed to bring every launch template into alignment with the finalized visual language, verify readability at common viewport sizes, and ensure rendering performance meets acceptable thresholds. Launching without this pass risks a first impression of visual incoherence.

Context

• Launch templates were created across multiple milestones and likely contain accumulated inconsistency.
• By M3, the visual language should already be defined, so this task is about conformance and polish rather than invention.
• The work should consider readability, consistency, and output size/performance together.

Possible Solutions

• A - Trust earlier milestone work and skip a dedicated launch polish pass: efficient, but risky for coherence.
• B - Revisit the whole visual language again during launch prep: more freedom, but too destabilizing.
• C - Recommended: run a structured launch-quality pass against the template set, fixing inconsistencies against the locked visual language and performance thresholds.

Plan

1. Define the launch review checklist for readability, consistency, and render efficiency.
2. Audit the launch template set against that checklist and record issues by chart family.
3. Apply the highest-value fixes and re-review the changed outputs.
4. Capture remaining non-blocking polish items as post-launch follow-ups.

Implementation Progress

• Confirm scope and acceptance with milestone owner.

• Milestone readiness signal is updated.

• Track blockers and mitigation owner.

Review Feedback

• [ ] Review cleared