Dual style packages

Problem

Once the basic chart batch exists, the next risk is carrying one accidental default look into every subsequent chart. At the same time, a pile of ad hoc visual options would blur the structure/theme boundary and create noise rather than clarity. This work should prove that the library can support at least two intentionally different style packages that change both scaffold and paint while remaining recognizably part of the same system.

Context

• The chart design philosophy already separates structure from theme; this task should use that split rather than collapsing visual language into one undifferentiated config blob.
• This belongs after the basic chart batch, not inside the first pilot-foundation milestone.
• The value of this task is comparative: the same chart batch should read differently under each package.

Possible Solutions

• Single default style with many knobs. Easier to ship, but weak for design learning and hard to evaluate intentionally.
• Many micro-themes. Useful for exploration, but too diffuse for this stage.
• Recommended: two opinionated packages with clear identities and paired structure-plus-theme behavior: a minimal analytic package and an expressive editorial package.

Plan

• Define the visual intent and structural rules for each package.
• Apply both packages across the shared chart batch.
• Compare where the package differences feel meaningful versus decorative.
• Capture the decisions that should persist into later visual-language work.

Implementation Progress

• Package 1: minimal analytic, inspired by Cleveland-style statistical graphics.
• Package 2: expressive editorial, inspired by Economist-style charts.
• Requirement: differences must include structure decisions such as axis posture, grid treatment, legend handling, or titling defaults, not just palette changes.

QA Exploration

• [ ] QA exploration completed (or N/A for non-UI tasks)

Review Feedback

• [ ] Review cleared