feat(chatbot): ADR-0038 L3 — build-health line under the Published card#1637
Merged
Conversation
onPublishDrafts may now return { ok, health } where health carries the
publish response's seedApplied + runtime probes (publishPackageDrafts'
new `probes` report, framework#1715). The Published card then renders a
build-health line: rows of sample data live, views/widgets/seeds verified
when probes ran clean, and each runtime finding (empty_query,
seed_not_applied, …) loudly — 'Published' and 'actually works' become two
separately-verified statements.
- publishHealthFromResponse: shared extractor (dispatcher-envelope
tolerant) used by ConsoleFloatingChatbot + AiChatPage;
- legacy boolean returns keep working (no health line);
- {ok:false} counts as failure (no Published badge).
Co-Authored-By: Claude Fable 5 <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 free
to 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.
Second half of BVL Phase 2 (ADR-0038), pairing with framework#1715 (post-publish runtime probes): the chat now shows what a publish actually did at runtime, so "Published" and "actually works" are two separately-verified statements.
What
onPublishDraftsmay return{ ok, health }—PublishHealthcarries the publish response'sseedApplied+probes(framework#1715). Legacyboolean/voidreturns keep working;{ok:false}counts as failure (no Published badge).ChatbotEnhancedrenders a build-health line under the Published badge:12 sample rows live · 3 views · 4 widgets verified— the "verified" claim appears only when probes ran clean;empty_query,seed_not_applied,view_read_failed, …) and the seed-load failure rendered loudly;probes_unavailable) so silence never reads as "probed and passed".publishHealthFromResponse: shared, dispatcher-envelope-tolerant extractor; both hosts (ConsoleFloatingChatbot + AiChatPage) wired to return structured outcomes.No health data → no element (older runtimes degrade silently).
Tests
{ok:false}→ no Published badge.publishHealthFromResponse: envelope tolerance, seedError mapping, undefined for older runtimes.Staging note: this card would have flagged today's live incident (publish reported success; the published app was unreadable minutes later — kernel-eviction metadata loss, diagnosed separately) as soon as L3 probes flow through a cloud .framework-sha bump.
🤖 Generated with Claude Code