Uh oh!
There was an error while loading. Please reload this page.
feat(ai-build): deferred-rule card section + richer propose wait hints - #2039
Merged
Conversation
…icher wait hints Two magic-flow confirm-step polish items observed in live testing: 1. Deferred/"not yet built" business rules (e.g. row-level "技师只看自己的工单" that the build defers to a later flow/permission pass) were mixed in with ordinary design-note assumptions in the Proposed-plan card, so users could mistake a deferred rule for one that was actually built. `classifyAssumptions` now keyword-splits assumptions, and the card renders the deferred ones under a distinct "待补 / Not yet built" section, apart from regular assumptions. 2. The propose/apply wait could run minutes under load while the rotating hint pool was small enough to repeat noticeably. Expanded the "Designing your app…" hint pool (relationships, forms, defaults, dashboard, review) so a long wait keeps showing fresh, concrete progress instead of looping the same few lines. Both are presentational + i18n (zh+en). Tests: plugin-chatbot 156 (+14: classifyAssumptions split + deferred section render + hint pool), app-shell 941. plugin-chatbot builds clean. 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.
Two magic-flow confirm-step polish items from live testing (follow-ups to #2036).
1. Deferred rules get a distinct "Not yet built" section
The Proposed-plan card listed all
assumptionstogether, mixing design notes ("设备通过所属客户建立归属关系") with deferred business rules ("技师只看自己的工单 — 需要后续单独补权限/流程配置"). Users could mistake a deferred rule for one that was built.classifyAssumptionsnow keyword-splits them, and the card renders deferred ones under a distinct 「待补 / Not yet built」 section. (Pairs with cloud-side honesty prompt + the trim-prose change.)2. Richer wait hints
The "Designing your app…" rotating hint pool (added in #2036) was small enough to visibly repeat during long (minutes, under load) propose/apply waits. Expanded the pool (relationships, forms, defaults, dashboard, review) so the wait keeps showing fresh, concrete progress.
Both presentational + i18n (zh+en).
Tests
plugin-chatbot156 (+14:classifyAssumptionssplit, deferred-section render, hint pool),app-shell941, plugin-chatbot builds clean (incl. DTS). (DOM/unit verified; the live AI-build chat isn't reproducible in app-showcase — same E2E caveat as #2036.)After merge: needs framework
.objectui-shabump + cloud pin to reach the running stack.🤖 Generated with Claude Code