fix(plugin-chatbot,app-shell): keep an assistant answer's chart after a reload - #27396

Requested by Warren · project thread
Fixes #25908

Clause-②: yes (widening)
Metadata-protocol: none

维护者速读

• 改了什么:AI 助手回答里的图表,刷新页面后不再消失;从服务器历史和本地缓存恢复时都会按原位置画回来。
• 为什么改:直播流里的图表是一次性的,服务器不存它;服务器存的是 visualize_data 工具结果,里面的 chart 字段就是同一份图表描述,之前没人读它。
• 风险与回滚:只影响聊天消息的恢复路径;没有 chart 字段的旧结果照旧不画图;回滚即 revert 本 PR。
• 先看:ui/packages/plugin-chatbot/src/mapMessages.ts(唯一读 chart 的地方与防重复画图规则)、ui/packages/app-shell/src/hooks/useChatConversation.ts(缓存写法)、ui/packages/plugin-chatbot/src/useObjectChat.ts(API 模式重建)。
• 两分钟验证:pnpm --dir ui exec vitest run packages/plugin-chatbot/src/__tests__/mapMessages.persistedChart-25908.test.ts packages/plugin-chatbot/src/__tests__/useObjectChat.persistedChart-25908.test.tsx packages/app-shell/src/console/ai/__tests__/AiChatPage.persistedChart-25908.test.ts,预期三个文件全绿。
• 需要你做的:无,席位落地。

What changes

An assistant answer that drew a chart came back as text only after a reload. The live stream draws the chart from a transient data-chart part that the server never stores. What the server stores is the visualize_data tool result, one JSON string whose chart key holds the same descriptor the part carried (#26744, comment 6457382770). Nothing read that key back.

• One reader (plugin-chatbot mapMessages.ts, chartFromToolResult). It reads chart off a visualize_data result through the existing parseResultEnvelope, and narrows it with the same chartFromDescriptor the data-chart part goes through, now shared by both. The top-level rows (a 20-row narration preview) are never drawn. A result stored before the producer wrote chart gives no chart, with no rebuild from its other keys.
• Where it sits. extractCharts reads tool results only for a message that has no data-chart part. A live message carries both, so it still draws the chart once. A stored message carries only the result, so each chart takes the offset of its tool part among the text parts.
• Hydration (app-shell hydratedMessagesToChatMessages) sets charts from chartsFromParts(message.parts). That walk covers both the server's visualize_data results and the cache's data-chart parts, and the offsets index the same text join the hydration makes content. The share page (SharedRecordPage) renders these messages directly, so it gets the chart too, with no change to its file.
• API-mode round trip (useObjectChat aiInitialMessages). The rebuild used to write one text part and then the tools, so a hydrated charts key was dropped. It now writes chartAnswerParts(content, charts): the text cut at each chart's offset, with a data-chart part between the runs. The mapper reads that back as the same content and the same charts at the same offsets.
• Cache (app-shell sanitizeChatMessagesForCache). It writes the same chartAnswerParts in place of the single text part, so a cache-fallback reload keeps the chart and its place. A tool-output arm would not have kept the place, because a tool part carries no position in the cache.
• Where the fix sits, and why. The order offered two places: the rebuild emits data-chart parts, or mapMessages re-derives charts from the tool output. This PR takes the first for the round trip and the cache, because the live path already draws from data-chart parts and only position-encoded parts keep textOffset through a rebuild that joins text. The one reader of chart sits in mapMessages, and the hydration mapper reaches it through chartsFromParts.
• Tool name. @objectstack/spec declares visualize_data only as a member of PLATFORM_TOOLS_BY_PACKAGE['service-ai'], with no constant of its own. mapMessages keeps one literal, VISUALIZE_DATA_TOOL (a module export, not a package export), and a test pins it to that registry.
• New exports (Clause-②: yes (widening), claim 6487631480): chartsFromParts, chartAnswerParts and the ChartAnswerPart type, on @object-ui/plugin-chatbot and @object-ui/plugin-chatbot/core. app-shell is private and needs to call the one reader, so these exports are how it does.

Tests

• plugin-chatbot mapMessages.persistedChart-25908.test.ts. A stored result yields the same chart the live part draws (title, series labels, all 30 rows rather than the 20-row preview), at the offset of its tool part. A bare string result is read too. A result without chart gives no chart and does not throw, and neither does a non-JSON one. Only visualize_data is read, and its name is pinned to the spec registry. A live message with both the part and the result draws one chart. chartAnswerParts maps back to the same message, and a chart without an offset follows the text.
• plugin-chatbot useObjectChat.persistedChart-25908.test.tsx. In API mode, a hydrated answer keeps one chart at its offset through the store, and the bubble draws it once, between the two text runs.
• app-shell AiChatPage.persistedChart-25908.test.ts. Server history restores the chart between the text it sat between, and a result without chart restores text and tool with no chart. A live answer is cached and restored with its chart in place, and a restored server answer survives being cached again.

Acceptance notes

• The reach has never been measured in a running console, and the producer change (cloud abffd69) runs on hosted deploys only (@objectstack/service-ai 10.3.0 on npm predates it). The proof here is fixture-level, against the result shape cloud: state the persisted visualize_data result shape after cloud#3292 (chart descriptor key, row cap), so ui can redraw charts after a reload #26744 read on cloud main a32c80c.
• The fixtures use the AI SDK text output wrapper ({ type: 'text', value }), the form a string tool result takes, and a bare string. A JSON-wrapped output ({ type: 'json', value }) with no status key resolves to the wrapper in the shared parseResultEnvelope, so it would give no chart. The producer returns a string, so that shape is not reached, and this PR does not change the shared parser.
• Local mode (no api) keeps dropping hydrated render-only keys in normalizeMessages, charts and buildProgress alike, as before. AiChatPage runs local mode only with no chat backend, which has no stored conversations.

Verification

All readings below were taken on head e1f1c06a, branched from origin/main c4c515ad. The four commits main gained since touch none of this PR's files.

node scripts/check-adr-0087-registration.mjs --base origin/main :: exit 0
node scripts/check-adr-0087-registration.mjs --self-test :: exit 0
node scripts/check-changeset-no-major.mjs --base origin/main :: exit 0
node scripts/check-closing-keyword-parity.mjs :: exit 0
node scripts/check-closing-keyword-parity.mjs --self-test :: exit 0
node scripts/check-comment-mask-corpus.mjs :: exit 0
node scripts/check-empty-changeset.mjs --base origin/main :: exit 0
node scripts/check-empty-changeset.mjs --self-test :: exit 0
node scripts/check-sdui-manifest.mjs :: exit 0
node scripts/check-sdui-manifest.mjs --self-test :: exit 0
node scripts/pm/release-rehearsal-clone.mjs --self-test :: exit 0
node scripts/release-pending-publish.mjs --self-test :: exit 0
pnpm --filter @objectstack/spec run check:duration-unit-keys :: exit 0
pnpm check:changeset-gate-self-tests :: exit 0
pnpm check:closed-ceremony-text :: exit 0
pnpm check:cross-package-test-inputs :: exit 0
pnpm check:dispatcher-error-vocabulary :: exit 0
pnpm check:driver-memory-census :: exit 0
pnpm check:engine-double-contract :: exit 0
pnpm check:error-status-conformance :: exit 0
pnpm check:gitlink-declared :: exit 0
pnpm check:nul-bytes :: exit 0
pnpm check:pm-changeset-deadline-census :: exit 0
pnpm check:published-files :: exit 0
pnpm check:query-options-erasure :: exit 0
pnpm check:refd-timer-probe :: exit 0
pnpm check:skill-identifier-liveness :: exit 0
pnpm check:test-source-alias :: exit 0
pnpm check:tier-file-adoption :: exit 0
pnpm check:type-check-coverage :: exit 0
pnpm check:type-check-debt :: exit 0
pnpm check:undeclared-dep-imports :: exit 0
pnpm check:watch-hint-literal :: exit 0
pnpm check:where-matcher :: exit 0
pnpm --dir ui exec vitest run scripts/ :: exit 0

Families CI owns (the required checks) are cited from this PR's check runs at hand-back; they were not re-run locally.

Human Minimum

• 1. Schemas start as Zod; packages/spec holds no runtime logic. (No packages/spec change.)
• 2. Every name I added uses the casing for its kind.
• 3. No formatter ran; pnpm lint passes. (eslint on the touched files: 0 errors; the repo-wide run is CI's.)
• 4. One issue, one branch off an up-to-date main, one pull request.
• 5. A change that publishes carries a changeset, and both declaration lines are filled in here and in the changeset.
• 6. packages/spec touched: not applicable.
• 7. No hand edits to content/docs/references/, packages/*/CHANGELOG.md or content/docs/releases/.
• 8. Title, body and comments are in English, apart from the 维护者速读 block the dispatch order asks for.

Generated by Claude Code