Consolidate semantic chart defaults and rendering control-surface follow-ons

Problem

Bundle the recent chart-rendering follow-on backlog into one M2 task covering semantic axis behavior, temporal-axis labeling/grouping, orientation-aware bar behavior, quantitative domain/headroom defaults, coordinated comparable-chart domains, optional semantic title fallback, and the chart-text control surface needed to expose these behaviors coherently through Dataface.

Context

• These nine recent graph-library tasks all came out of the same M1 structure-lab critique and are all currently not_started p2 follow-ons:
• tasks/workstreams/graph-library/archive/add-advanced-typography-controls-for-vega-generated-chart-text.md
• tasks/workstreams/graph-library/archive/add-coordinated-scale-domains-for-comparable-charts.md
• tasks/workstreams/graph-library/archive/add-orientation-aware-bar-direction-and-grid-defaults.md
• tasks/workstreams/graph-library/archive/add-quantitative-scale-headroom-defaults-for-standard-charts.md
• tasks/workstreams/graph-library/archive/add-temporal-axis-label-semantics-for-point-vs-interval-positioning.md
• tasks/workstreams/graph-library/archive/implement-grouped-temporal-axes-for-weekly-ticks-and-monthly-labels.md
• tasks/workstreams/graph-library/archive/investigate-auto-generated-chart-titles-from-axis-semantics.md
• tasks/workstreams/graph-library/archive/investigate-horizontal-bar-orientation-preserving-semantic-axes.md
• tasks/workstreams/graph-library/archive/research-temporal-axis-grouping-for-weekly-ticks-and-monthly-labels.md
• They are all too detailed and design-system-shaped for m1-ft-analytics-analyst-pilot. The M2 workstream definition is a better fit because it explicitly includes semantic-type-aware behaviors and exposed chart properties.
• The common theme is not one chart-family bug. It is the next layer of chart-library productization:
• semantic axis and orientation behavior
• temporal-axis semantics and grouped labeling
• quantitative domain policy and comparable-chart coordination
• optional generated defaults such as fallback titles
• the author-facing control surface needed to expose these behaviors coherently
• The goal of this task is triage and backlog shaping, not immediate implementation of every subtopic. We want one active M2 backlog item with enough detail to guide later execution, while preserving the narrower notes as reference material.
• Likely implementation and design touchpoints remain:
• dataface/core/render/chart/standard_renderer.py
• dataface/core/render/chart/presentation.py
• dataface/core/render/chart/pipeline.py
• dataface/core/render/chart/decisions.py
• dataface/core/render/chart/DESIGN.md
• chart property and authoring docs under docs/docs/reference/

Possible Solutions

• Keep the nine follow-ons as separate M1 tasks and only retag their milestone. This preserves detail, but it keeps the backlog noisy and still overstates how execution-ready these items are.
• Merge everything into one giant implementation task and delete the narrower notes. This reduces clutter, but it throws away useful design context and makes later execution harder to split back into focused work.
• Recommended: create one M2 umbrella task for semantic chart defaults and rendering control-surface follow-ons, then archive the nine leaf tasks as superseded reference notes. This keeps the active backlog legible, moves the work to the right milestone, and preserves the detailed problem framing for later decomposition once M2 scope is clearer.

Plan

1. Create one new graph-library M2 task that summarizes the shared theme across the nine follow-ons.
2. Place the new task under m2-internal-adoption-design-partners and associate it with m2-semantic-type-behaviors, since the main value is semantic chart behavior rather than pilot-critical chart availability.
3. Preserve the nine original tasks as archived reference notes with a clear superseded banner pointing back to this umbrella task.
4. Treat the archived notes as a source inventory for later execution. If implementation eventually needs finer granularity, split from this umbrella back into smaller M2 tasks based on real design-partner pressure rather than pre-emptive backlog fragmentation.
5. Keep QA marked N/A for now because this task is backlog curation, not a shipped UI change.

Implementation Progress

• 2026-03-27: Created this umbrella task to replace nine narrow M1 follow-ons that were all generated during structure-lab critique.
• 2026-03-27: Chose m2-internal-adoption-design-partners as the correct milestone because the work is about semantic defaults, control surfaces, and coherent chart behaviors rather than M1 pilot minimums.
• 2026-03-27: Chose m2-semantic-type-behaviors as the closest existing initiative, with the understanding that the typography/control-surface portion also informs the neighboring M2 chart-properties initiative.

QA Exploration

• N/A. This task only consolidates backlog items and retargets milestone ownership; it does not ship a runtime UI change.

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

Review Feedback

• [ ] Review cleared