Uh oh!
There was an error while loading. Please reload this page.
feat(chatbot): surface seed-apply results, fix stale Running badge, Open-app on build done - #1625
Merged
Conversation
…pen-app on build done Three magic-moment polish items: 1. seedApplied surfacing — the framework now materializes published `seed` rows on every publish path and reports under `seedApplied` (never thrown). Surface a failure as a warning toast in BOTH publish surfaces (floating chat + AI chat page) and the home pending-drafts banner, so "Published!" can never again hide silently empty tables (the staging "No rows" incident). The banner also publishes structure before seeds and `publishDraft()` now returns the server result (envelope-tolerant). 2. Stale "Running" badge — a conversation persisted mid-stream can carry `input-available` next to a present output; reloading then showed a finished build as Running forever. mapMessages now promotes such parts to `output-available` (output present = the call finished). 3. "Open app" on the build tree — a finished build that created an `app` renders an Open-app action (new optional `onOpenBuiltApp` prop), wired in both hosts to navigate straight into the just-built app. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…ction Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
✅ Console Performance Budget
📦 Bundle Size Report
Size Limits
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three magic-moment polish items, companion to framework#1686:
1. Surface
seedApplied(companion to framework#1686)The framework now materializes published
seedrows on every publish path and reports underseedApplied— never thrown, so the UI must check it. This PR surfaces a seed-load failure as a warning toast in all three publish surfaces (floating chat, AI chat page, home pending-drafts banner), so "Published!" can never again hide silently empty tables (the staging "No rows" incident). The banner also publishes structure before seeds, andMetadataClient.publishDraft()now returns the server result (envelope-tolerant).2. Stale "Running" badge on reloaded conversations
A conversation persisted mid-stream can carry
input-availablenext to a present output (the terminal state was never snapshotted) — reloading then showed a finished build as Running forever.mapMessagesnow promotes such parts tooutput-available(output present = the call finished). Live streams without output keep their state.3. "Open app" on the finished build tree
A finished build that created an
appnow renders an Open app → action on theBuildProgressPanel(new optionalonOpenBuiltAppprop), wired in both hosts to navigate straight into the just-built app.Test
plugin-chatbot 57, data-objectstack 14, app-shell 390 — all green; typechecks clean on all three packages.
🤖 Generated with Claude Code