Frontend: make Chat workflow run state and next actions explicit#2702
Open
AbigailDeng wants to merge 1 commit into
Open
Frontend: make Chat workflow run state and next actions explicit#2702AbigailDeng wants to merge 1 commit into
AbigailDeng wants to merge 1 commit into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## dev #2702 +/- ##
==========================================
- Coverage 83.84% 83.84% -0.01%
==========================================
Files 1248 1248
Lines 95522 95522
Branches 12528 12528
==========================================
- Hits 80089 80088 -1
Misses 9871 9871
- Partials 5562 5563 +1
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
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.
Problem
Closes #2700.
Chat workflow creation already streamed status into message bodies, but the primary run state and next action stayed fragmented across a small header tag, collapsed message disclosures, and the red stop button in the composer. Users had no single place to see what the current chat run is doing, whether operator action is required, and what they should do next.
Solution
Impacted Paths
apps/aevatar-console-web/src/pages/chat/index.tsxapps/aevatar-console-web/src/pages/chat/index.test.tsxapps/aevatar-console-web/src/locales/en-US.tsapps/aevatar-console-web/src/locales/zh-CN.tsValidation
Passed:
pnpm --dir apps/aevatar-console-web tscpnpm --dir apps/aevatar-console-web test:ui --runTestsByPath src/pages/chat/index.test.tsx --runInBandpnpm --dir apps/aevatar-console-web buildgit diff --check -- apps/aevatar-console-webbash tools/ci/test_stability_guards.shObserved but not fixed in this PR:
pnpm --dir apps/aevatar-console-web test:uistill fails on existing non-Chat suites, includingsrc/pages/teams/home.test.tsx,src/pages/scopes/invoke.test.tsx, andsrc/pages/studio/components/bind/StudioMemberBindPanel.test.tsx. These failures were not introduced by the Chat diff and were left out of scope for this issue-focused PR.Frontend Boundary Check
apps/aevatar-console-web/**.Browser Verification
http://localhost:5178/chat?scopeId=scope-aredirected to/login, so the authenticated Chat surface was not reachable in this environment.FKST Provenance
aevatar-frontend-fkst#2700/Users/abigaildeng/.codex/worktrees/fkst-issue-2700feat/2026-07-10_chat-run-status-center1de88c63c