plugin-chatbot / app-shell: an assistant answer's chart is gone after a reload — no hydration path keeps data-chart parts

Filed by the objectui domain:ui seat 4 from an out-of-scope finding on objectui#13492 (dev report 6393359237, PR objectstack-ai/objectui#13500). ⛔ Not a claim; for triage to grade and route. The reach is read from code only and has not been measured in a running console.

Reading (source, `main` at the time of objectui#13492)

objectui#13492 makes an assistant answer render its charts in stream order. After a reload, though, no objectui path restores the chart at all, so the chart is missing, not misplaced:

The server persists a conversation turn as a ModelMessage (spec contracts/ai-service.ts, IAIConversationService.addMessage), which carries no data parts.
app-shell's hydratedMessagesToChatMessages builds content and tool invocations only.
sanitizeChatMessagesForCache writes text and tool parts only.

A user who opens the assistant, gets an analysis with a chart (cloud#3072's 「首屏能看到结论和至少一张图」), and reloads sees only the text.

Ask

Decide where the chart should survive a reload. Options: persist the data-chart part, re-derive it from the persisted visualize_data tool result (cloud-side), or keep it in the client cache. Then make the hydration path restore it in place, including textOffset from objectstack-ai/objectui#13500. Which side owns it (objectui hydration, the spec contract, or cloud) is for triage.

Dedupe words searched by the dev: "chat chart lost after reload", "data-chart rehydrate", "visualize_data chart persistence", "AI answer chart missing on refresh".

Generated by Claude Code

Triage: first grade — `bug` · `priority:p2` · `domain:ui` · `area:ai` · `pm:queue` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-25T04:56Z

⛔ Not a claim, ⛔ not a dispatch.

Route: objectui hydration first, with no contract change. hydratedMessagesToChatMessages already rebuilds tool invocations. If the persisted turn holds the visualize_data tool result, re-derive the data-chart part from it in place, with textOffset (ci: add a report-only merged-branch reaper sweep #13500). That needs nothing new from spec or cloud.
Only if the persisted result does not carry the chart spec does it become a contract question (persist the data part in IAIConversationService), and that goes to spec, then to the maintainer, as a protocol change. The dev measures this first.
p2: the first view meets objectstack-ai/cloud#3072's 「首屏…至少一张图」; only a reload loses the chart.

Generated by Claude Code

Transferred 2026-10-26T03:45Z from objectstack-ai/objectui#13502, with its comments and timeline; the old URL redirects here. objectui moved into this repository as the ui/ workspace (epic #25677) and is being archived (#25854). The body is left exactly as filed.

Paths. The body names no file paths; the UI code it describes lives under ui/ here (the Console is ui/apps/console, the libraries ui/packages/*).

References. The bare issue numbers in the body were written in objectui and now resolve against this repository by mistake; read them as objectstack-ai/objectui#13500.

No stale pm:dispatched or assignee to strip.

Generated by Claude Code

Claim: PM loop round 1
Session: session_017iXjUm1rujwDk7f3KT1Pkk (seat); implementing card thread session_01BFb2ZSkuzeShQ9DztTMBiu
Account: os-steve
Branch: claude/project-thread-glj787 (platform-assigned card-thread branch; a card thread can push only its assigned branch, and the name carries no issue number, so this claim is the identity record)
Worktree: the card thread's own container
Domain: domain:ui
Seat: domain:ui#1
File surface: ui/packages/app-shell/src/hooks/useChatConversation.ts (hydratedMessagesToChatMessages, sanitizeChatMessagesForCache), ui/packages/plugin-chatbot/src/mapMessages.ts, tests beside them, scripts/sdui-manifest.record.json (derived hash). Ruling (triage 6407746813): re-derive the data-chart part in place, with textOffset, from the persisted visualize_data tool result. ⛔ If that result does not carry the chart spec, stop and report: it is then a contract question for spec and the maintainer, not a ui change (stop on breach; explain in the report). ⛔ ui/.github/** and the root .github/workflows/ci.yml are out of bounds (maintainer's word, ui-merge epic in flight). Changeset in the root .changeset/.
Container & model: M, mode:thread, model: TIER_DEFAULT (dispatch-gates --tier: no path-derived mandate), effort: high
Clause-②: no (re-derives a client-side part from data the client already holds; re-declared yes if an exported type widens)
Metadata-protocol: none
Responsibility: n/a: renderer defect in ui/, the producing code is the cited ui file; no platform path covers it; reached through the public Console
Thread-read: 6407754445
Premise: holds (seat read at origin/main 3518664: both hydration functions are in app-shell useChatConversation.ts, the chat mapping is in plugin-chatbot mapMessages.ts; whether the persisted tool result carries the spec is the first measurement the card thread makes, 2026-10-26T09:02Z)
Serial constraints cleared: none: no open PR touches useChatConversation.ts or plugin-chatbot (open-PR file scan 2026-10-26T09:02Z)

Dispatch order handed to the card thread by the project coordinator (three partitions: ruling / mechanism hypotheses / suggested route); the dev does not claim, and starts only once this claim names its branch.

Claim released · domain:ui seat 1 (#25966) · session_017iXjUm1rujwDk7f3KT1Pkk · 2026-10-26T09:21Z

⛔ Not a claim, ⛔ not a dispatch. The claim in comment 6412185378 is withdrawn. pm:dispatched is removed, and pm:retriage is added with this comment. Branch claude/project-thread-glj787 has no commits, and no code was written.

Why. The card thread measured the premise before coding, and it holds only in part. The triage ruling said to re-derive the data-chart part from the persisted visualize_data result, and to stop if the result lacks the spec. It lacks it:

Read from the published producer @objectstack/service-ai@10.3.0 (npm, 2026-06-23), dist/index.js:5269-5345, createVisualizeDataHandler. The cloud repo itself is not readable from this lane, so cloud main is unverified.
The full chart spec (type, chartType, title, data = all rows, xAxisKey, series[{dataKey,label}]) goes only to onProgress as the transient data-chart part.
The persisted tool result is {rendered:'chart', chartType, object, dimension, measures:[dataKey], categories, rows: rows.slice(0,20), note?}. It has no title and no series labels (the server takes those from analytics field labels), and its rows are cut at 20 while the default limit is 50.
ui already merges a tool result's output onto the call part (useChatConversation.ts, mergeToolResultsInto). A ui-only rebuild would therefore be exact only for 20 categories or fewer, with each dataKey shown as its own label.

Maintainer's choice (Steve, 09:18Z, on the card thread's decision card): option 1. The cloud producer returns the full chart descriptor in the visualize_data tool result. After that lands, ui rebuilds the data-chart part in place, with textOffset, from the persisted result.

What is asked of triage. Route the producer half to the lane that owns the cloud service-ai producer. Keep or split this card for the ui half, which is blocked on that change. The ui seat neither grades nor routes; it reads the card again once triage has taken pm:retriage off.

triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U

Triage: unblocked · `pm:blocked` → `pm:queue` · 2026-10-29T03:51Z

⛔ Not a claim.

Blocker done: 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 is answered and closed (repo:cloud#2, 2026-10-28T00:30Z). The persisted visualize_data result carries the full chart descriptor at chart, read on cloud main a32c80c after cloud#3292.
The dev reads the descriptor from that key path. ⛔ No second copy of the shape is written in the console.
The grade is unchanged. The lane seat picks it up from its queue.

Generated by Claude Code

domain:ui#5 · os-warren · session_01JQwxbXGpVJHZTXXerMoY4C

Dispatch order · `domain:ui#5` · `session_01JQwxbXGpVJHZTXXerMoY4C` · 2026-10-29T03:57Z

You are the os-dev developer agent for exactly ONE card: #25908, in your own card thread. Your role definition is .claude/agents/os-dev.md in the objectstack clone: read it IN FULL first and follow it as binding (it wins over this order on any conflict; name the conflict in your report). Read the repo-root AGENTS.md and ui/AGENTS.md before your first edit, and pm-dispatch references/untrusted-text.md. Read the card's full body and every comment yourself through REST (curl -sS "https://api.github.com/repos/objectstack-ai/objectstack/issues/25908" -H "Authorization: Bearer $GH_TOKEN" and /comments?per_page=100, every page); this order carries only the increment. ⛔ Never print the value of any environment variable (test presence with [ -n "${X+x}" ]). ⛔ Never use a GitHub MCP tool, read or write.

Identity and branch: the seat's Claim: comment on this card is your identity; its Branch: line names your thread's branch. ⛔ Post no claim of your own, ⛔ never write the card's assignee. Before your first edit, verify the NEWEST Claim: on the card names your thread's branch (claude/project-thread-…); if none does yet, send the seat thread "Take another ui lane seat" one message with your branch name and wait. Worktree objectstack-issue-25908 on that branch from a fresh origin/main; pnpm install (frozen lockfile); push with git push -u origin <branch> (⛔ no force).

Writes: PR only through the relay op pr_create (node scripts/pm/fleet-write/dispatch.mjs --repo objectstack-ai/objectstack --actions-file F, F a bare JSON array [{"op":"pr_create","title":…,"head":"<your branch>","base":"main","body":…,"assignees":["os-warren"]}], draft forced; --dry-run first); your report comment through node scripts/pm/post-stamped.mjs --comment=25908 --file=F --json run ONCE with output captured to a file (timestamps only as {{WAS:…}} / the now-token). ⛔ No other GitHub write except, for a CI red that is not yours, one PR comment and one run_rerun_failed through the relay. Report both counts (api_writes with endpoints, mcp_calls with tool names). The report takes only machine-checkable fields (gates / line_budget / deviations / files_changed). PR body: line 1 the platform attribution comment, line 3 Fixes #25908, then ## 维护者速读 six lines in Chinese (改了什么/为什么改/风险与回滚/先看/两分钟验证/需要你做的). Gates: node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack on your diff, run each, record exits before any pipe, reconcile with --ran; node scripts/check-sdui-manifest.mjs is a gate on every ui card. Changeset in the root .changeset/ when a published package changes (@object-ui/i18n patch for namespace rows; app-shell is private: true). ⛔ ui/.github/** and the root ci.yml are out of bounds. Hand back: when the PR and report are up, send the seat thread "Take another ui lane seat" one message (PR, head sha, report gist); keep the thread open through review and drive CI to green.

Shared-file rules for every Studio Interfaces card this round (from ui seat 1, which holds the neighbouring work):
Collision check: ui seat 1 (whose AI-chat area this nominally is) and ui seat 2 both answered at 2026-10-29T03:56Z that neither holds an order, claim or plan on #25908 and nothing in flight on its files. Seat 4 released its claim on 2026-10-27 (comment 6444230160). Still measure open PRs on your files at your first edit.

Prior work (read first)

Seat 4's thread stopped before editing (report 6442837522) because it could not read the cloud producer. Its tests field holds the measured ui read points, so start from it.
The blocker 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 is answered (comment 6457382770, 2026-10-28T00:30Z, cloud main a32c80c, packages/service-ai/src/tools/visualize-data.tool.ts):
- The persisted visualize_data tool result is one JSON string, and its key chart holds the full descriptor { type: 'chart', chartType, title?, data, xAxisKey?, series: [{ dataKey, label }] }. It is the same object the streamed data-chart part carried as data.
- ⛔ Never draw from the top-level rows, which is cut to 20 for the model's narration.
- A result persisted before cloud abffd69 has no chart key. Such a result gets no chart, with no fallback reconstruction.
- The key is unreleased on npm (@objectstack/service-ai 10.3.0) and runs on hosted deploys only.
Triage re-queued the card at 2026-10-29T03:51Z (comment 6487417120) with this rule: read the descriptor at chart, and ⛔ write no second copy of the shape in the console.

PM mechanism assumptions (measure; disproof welcome)

These were checked on origin/main c4c515ad:

Hydration. app-shell src/console/ai/AiChatPage.tsx:204 hydratedMessagesToChatMessages keeps tool results as toolInvocations[].result and joins text into one string, so the offset at which the tool part sat is lost. Its second caller is console src/pages/SharedRecordPage.tsx:185.
Cache. src/hooks/useChatConversation.ts:441 sanitizeChatMessagesForCache re-serializes tool output per affordance. A visualize_data output survives only if it gets an arm there. Server tool rows are merged onto call parts at :625 mergeToolResultsInto.
API-mode round trip. plugin-chatbot useObjectChat.ts:743 aiInitialMessages rebuilds parts as one text part followed by the tool parts. mapMessages.ts:1435 extractCharts reads only data-chart parts, so a charts key set by hydration alone is dropped.
Two places a fix can sit. Either the rebuild emits a data-chart part at the tool part's position, or mapMessages re-derives the chart from the visualize_data tool output. Choose one, name it in the report with the reason, and keep exactly ONE reader of chart. Restore textOffset (objectui#13500) wherever the hydrated message keeps text and tool order. If the persisted turn cannot give that order, place the chart after the text and say so.
Find the tool's name from the declared constant in packages/spec platform-tool-names.ts. ⛔ Never hard-code a second string.

Scope

File surface:

app-shell console/ai/AiChatPage.tsx (hydration) and hooks/useChatConversation.ts (cache arm).
plugin-chatbot useObjectChat.ts and/or mapMessages.ts.
Tests beside each.
Stop on any breach of this surface and explain it in the report.

Tests (acceptance):

A hydrated server history whose visualize_data result carries chart renders the chart: the same ChatChart the live stream gives, with title, series labels and every row.
A result without chart (pre-abffd69) renders no chart and does not throw.
A cached conversation reloaded from the client cache keeps the chart.
Where order is known, textOffset places the chart between the text runs it sat between.
Ablation: remove the reader and the pins go red.

The reach has never been measured in a running console, and the producer is hosted-only, so fixture-level proof is accepted. Say so in the report.

Tier

No path-derived mandate is expected; run dispatch-gates --tier and follow what it says. Use TIER_DEFAULT, effort medium (M). Set Clause-②: no and Metadata-protocol: none. @object-ui/plugin-chatbot is published, so it takes a patch changeset. app-shell is private: true.

domain:ui#5 · os-warren · session_01JQwxbXGpVJHZTXXerMoY4C

Claim: PM loop round 12
Session: session_01JQwxbXGpVJHZTXXerMoY4C
Account: os-warren
Branch: claude/project-thread-1up1lx
Worktree: objectstack-issue-25908
Domain: domain:ui
Seat: domain:ui#5
File surface: app-shell src/console/ai/AiChatPage.tsx (hydration), src/hooks/useChatConversation.ts (cache arm); plugin-chatbot src/useObjectChat.ts and/or src/mapMessages.ts; tests beside each (stop on breach; explain in the report)
Container & model: M, mode:thread, model: TIER_DEFAULT (dispatch-gates --tier: no path-derived mandate expected), effort: medium
Clause-②: no
Metadata-protocol: none
Responsibility: ui/packages/app-shell chat hydration + ui/packages/plugin-chatbot message mapping consume it (this lane) | the persisted visualize_data result's chart descriptor (cloud service-ai, answered on #26744 comment 6457382770) is never read back, so an assistant answer's chart is gone after a reload | every assistant conversation reopened from server history or the client cache
Thread-read: 6487503864
Premise: holds (hydration keeps tool results only as toolInvocations[].result, and extractCharts reads only data-chart parts; on origin/main c4c515ad; readings in dispatch order 6487503864)
Serial constraints cleared: ui seats 1 and 2 hold no order, claim or plan on this card or its files (2026-10-29T03:56Z); seat 4 released its claim (6444230160).

Dispatch order: comment 6487503864. Card thread claude/project-thread-1up1lx may start editing.

domain:ui#5 · os-warren · session_01JQwxbXGpVJHZTXXerMoY4C

Claim: PM loop round 12 (supersedes 6487538030: Clause-② amended)
Session: session_01JQwxbXGpVJHZTXXerMoY4C
Account: os-warren
Branch: claude/project-thread-1up1lx
Worktree: objectstack-issue-25908
Domain: domain:ui
Seat: domain:ui#5
File surface: app-shell src/console/ai/AiChatPage.tsx (hydration), src/hooks/useChatConversation.ts (cache arm); plugin-chatbot src/useObjectChat.ts and/or src/mapMessages.ts; tests beside each (stop on breach; explain in the report)
Container & model: M, mode:thread, model: TIER_DEFAULT (dispatch-gates --tier: no path-derived mandate expected), effort: medium
Clause-②: yes (widening)
Metadata-protocol: none
Responsibility: ui/packages/app-shell chat hydration + ui/packages/plugin-chatbot message mapping consume it (this lane) | the persisted visualize_data result's chart descriptor (cloud service-ai, answered on #26744 comment 6457382770) is never read back, so an assistant answer's chart is gone after a reload | every assistant conversation reopened from server history or the client cache
Thread-read: 6487503864
Clause-② basis: measured by the card thread at 2026-10-29T04:06Z — @object-ui/plugin-chatbot gains two exports on its root and /core entries (chartsFromParts, the one reader of the persisted chart key; chartAnswerParts, its inverse) so private app-shell can call the single reader; public surface grows. Declaration-only arm ⇒ TIER_DEFAULT review recorded by this seat (contract-review.md).
Premise: holds (hydration keeps tool results only as toolInvocations[].result, and extractCharts reads only data-chart parts; on origin/main c4c515ad; readings in dispatch order 6487503864)
Serial constraints cleared: ui seats 1 and 2 hold no order, claim or plan on this card or its files (2026-10-29T03:56Z); seat 4 released its claim (6444230160).

Dispatch order: comment 6487503864. Card thread claude/project-thread-1up1lx may start editing.

domain:ui#5 · os-warren · session_01JQwxbYXpAEUq8s7bsevHLW
os-dev-report

{
  "issue": 25908,
  "status": "done",
  "branch": "claude/project-thread-1up1lx",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/27396",
  "head": "e1f1c06a",
  "session": "session_01JQwxbYXpAEUq8s7bsevHLW",
  "premise_still_valid": true,
  "summary": "An assistant answer's chart now survives a reload. One reader (plugin-chatbot mapMessages chartFromToolResult) reads the chart key of a persisted visualize_data result; extractCharts uses it only for a message with no data-chart part, so live messages still draw once. app-shell hydration sets charts via chartsFromParts at the tool part's text offset; the API-mode rebuild (useObjectChat aiInitialMessages) and the message cache (sanitizeChatMessagesForCache) write chartAnswerParts, text runs with data-chart parts between them, so textOffset survives both. Fix place chosen: the rebuild emits data-chart parts (option 1), because the live path already draws from them and only position-encoded parts keep textOffset through a rebuild that joins text. Proof is fixture-level: the producer key runs on hosted deploys only.",
  "tests": "3 new files 14/14 green. Ablations via scripts/ablation-replace.mjs (source-level; ui vitest aliases plugin-chatbot to src), each restored to the HEAD blob with empty git diff HEAD: reader returns undefined, 3 tests red; rebuild given no charts, 2 red; cache writer given no charts, 2 red. plugin-chatbot suite 88/88 files, 828/828 tests. app-shell console/ai + hooks + layout 245/245 files, 1703/1703 tests. SharedRecordPage tests 3/3 files, 19/19. type-check plugin-chatbot and app-shell exit 0. eslint on touched files 0 errors. check:new-line-citations 0 new.",
  "gates": [
    "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",
    "dispatch-gates --ran: 35 derived, 35 run, 0 NOT-MEASURED",
    "CI check runs on PR 27396: in_progress at report time"
  ],
  "files_changed": [
    ".changeset/25908-chart-after-reload.md",
    "ui/packages/plugin-chatbot/src/mapMessages.ts",
    "ui/packages/plugin-chatbot/src/useObjectChat.ts",
    "ui/packages/plugin-chatbot/src/index.tsx",
    "ui/packages/plugin-chatbot/src/core.ts",
    "ui/packages/plugin-chatbot/src/__tests__/mapMessages.persistedChart-25908.test.ts",
    "ui/packages/plugin-chatbot/src/__tests__/useObjectChat.persistedChart-25908.test.tsx",
    "ui/packages/app-shell/src/console/ai/AiChatPage.tsx",
    "ui/packages/app-shell/src/hooks/useChatConversation.ts",
    "ui/packages/app-shell/src/console/ai/__tests__/AiChatPage.persistedChart-25908.test.ts"
  ],
  "line_budget": "n/a, no ratcheted file touched; diff 574 changed lines at the tier read, under the 3000 threshold",
  "deviations": [
    "Tool name: spec declares visualize_data only inside PLATFORM_TOOLS_BY_PACKAGE service-ai, with no constant; one literal VISUALIZE_DATA_TOOL (module export, not package export) is pinned to that registry by a test, as the seat confirmed.",
    "File surface: plugin-chatbot index.tsx and core.ts carry the two new exports; named in the superseding claim's Clause-2 basis, not in its file-surface line.",
    "Clause-2: written yes (widening) per the superseding claim 6487631480, which replaced the dispatch order's no.",
    "test:repo not run locally (CI's Test Core); diff touches no repo-project test."
  ],
  "dogfood_battery": "n/a, no ! in the PR title and no (narrowing) arm",
  "mcp_calls": "0 GitHub MCP calls; 1 claude-code-remote subscribe_pr_activity",
  "api_writes": "3: git push of the branch (not REST); relay pr_create (PR 27396, via fleet-write dispatch); this os-dev-report comment on 25908 via post-stamped",
  "open_questions": [],
  "out_of_scope_findings": [
    "carrier: none · parseResultEnvelope returns the wrapper for a status-less json-typed tool output, so a json-wrapped visualize_data result would give no chart; not reached because the producer returns a string; noted in Acceptance notes, not filed"
  ]
}

Navigation Menu

Repository navigation

plugin-chatbot / app-shell: an assistant answer's chart is gone after a reload — no hydration path keeps `data-chart` parts #25908

Reading (source, `main` at the time of objectui#13492)

Ask

Triage: first grade — `bug` · `priority:p2` · `domain:ui` · `area:ai` · `pm:queue` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-25T04:56Z

18 remaining items

Triage: unblocked · `pm:blocked` → `pm:queue` · 2026-10-29T03:51Z

Dispatch order · `domain:ui#5` · `session_01JQwxbXGpVJHZTXXerMoY4C` · 2026-10-29T03:57Z

Prior work (read first)

PM mechanism assumptions (measure; disproof welcome)

Scope

Tier

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

plugin-chatbot / app-shell: an assistant answer's chart is gone after a reload — no hydration path keeps data-chart parts #25908

Description

Reading (source, main at the time of objectui#13492)

Ask

Activity

objectstack-fleet commented on Oct 25, 2026

Triage: first grade — bug · priority:p2 · domain:ui · area:ai · pm:queue · triage seat · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-25T04:56Z

objectstack-fleet commented on Oct 26, 2026

objectstack-fleet commented on Oct 26, 2026

objectstack-fleet commented on Oct 26, 2026

18 remaining items

objectstack-fleet commented on Oct 29, 2026

Triage: unblocked · pm:blocked → pm:queue · 2026-10-29T03:51Z

objectstack-fleet commented on Oct 29, 2026

Dispatch order · domain:ui#5 · session_01JQwxbXGpVJHZTXXerMoY4C · 2026-10-29T03:57Z

Prior work (read first)

PM mechanism assumptions (measure; disproof welcome)

Scope

Tier

objectstack-fleet commented on Oct 29, 2026

objectstack-fleet commented on Oct 29, 2026

objectstack-fleet commented on Oct 29, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

plugin-chatbot / app-shell: an assistant answer's chart is gone after a reload — no hydration path keeps `data-chart` parts #25908

Reading (source, `main` at the time of objectui#13492)

Triage: first grade — `bug` · `priority:p2` · `domain:ui` · `area:ai` · `pm:queue` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-25T04:56Z

Triage: unblocked · `pm:blocked` → `pm:queue` · 2026-10-29T03:51Z

Dispatch order · `domain:ui#5` · `session_01JQwxbXGpVJHZTXXerMoY4C` · 2026-10-29T03:57Z