Skip to content

Teach the Planner its existing numerical chart capabilities - #447

Open
MaggieAppleton wants to merge 4 commits into
mainfrom
maggie/planner-chart-awareness
Open

MaggieAppleton wants to merge 4 commits into
mainfrom
maggie/planner-chart-awareness

Conversation

@MaggieAppleton

@MaggieAppleton MaggieAppleton commented Oct 10, 2026 •

Copy link
Copy Markdown
Collaborator

The Planner could deny all numerical chart support even though the deployed editor rendered it. Ordinary instructions named only three SeeCode diagram types, and the model also mistook a saved code block for an unrendered chart.

Expose the existing registry-derived catalogue (42 types and 15 aliases) to ordinary and Atomic Planner sessions, add labelled synthetic bar, Marimekko and dumbbell examples, variant-specific data requirements, and numeric evidence rules, and explain the canonical code-block representation. Prefer Chopin’s native SeeCode package whenever its catalogue can represent the information. Mermaid is only a fallback for a representation the native catalogue cannot provide or an explicit user request. Jev-selected diagrams remain SeeCode-only. Routing, flags, rendering and persistence are unchanged.

Validation: inventory, preference and alias-example regressions failed before their respective fixes. At a0910d48, 28 focused Planner/catalogue/renderer tests pass (719 expectations), including all six actual guide examples and all 15 renderer aliases. bun run fix, bun run ci and bun run types pass (31 existing lint warnings). The preceding a752c4b2 also passed 118 focused tests, including all 42 canonical edit/reopen cases. Current-head validation, e2e and container CI are pending.

Review repair: aliases are no longer described as interchangeable canonical payloads. marimekko requires columns with segments; dumbbell requires two values per category. The guide explains their purpose and input requirements with renderer-validated examples, and records the other numerical variants' meaning (such as ranks, bubble size and beeswarm packing). Canonical Jev selection criteria remain unchanged.

Production reproduction, before this fix: two hosted turns first refused charts, then saved an explicitly supplied bar chart with Alpha 12, Beta 7, Gamma 19. A fresh browser tab rendered those exact values.

Chart-awareness acceptance at fcc1bda9, local: one fresh real gpt-6-luna Copilot SDK turn chose and saved a native bar chart without chart syntax or type hints. It preserved a different synthetic dataset—North 17, South 9, East 23, West 14—and the saved source and rendered values survived a fresh browser context and server restart. This used production Chat/document/persistence code with synthetic GitHub boundaries and Jev off. The later native-first preference and alias guidance are covered by deterministic tests and have no additional live-model run. No deployment or merge was performed.

The trace retains a blocked repository-search attempt and an invalid insert index corrected within the same turn. A diagnostic SVG selector also matched toolbar icons; read-only recapture with the agent disabled passed. No further model turn was sent. This verifies the chart-awareness repair for one fresh case, not flawless tool use or all chart types in a live model.

What changes and what already worked

Registry-derived guidance repair and before-fix production chart reproduction

Corrected guidance: saved chart after fresh reopen

Real local-model output at fcc1bda9, before the native-first and alias-guidance follow-ups, on fresh synthetic data. Capture followed server restart with the agent disabled; Fit to width shows all four bars.

Corrected instructions produce a saved bar chart with North17 South9 East23 West14 in local real-model acceptance

@coolify-githubnext-app

coolify-githubnext-app Bot commented Oct 10, 2026 •

Copy link
Copy Markdown

The preview deployment for chopin is ready. 🟢

Open app | Open Build Logs | Open Application Logs

Last updated at: 2026-10-10 08:53:24 CET

@MaggieAppleton
MaggieAppleton enabled auto-merge (rebase) October 10, 2026 08:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant