Skip to content

Frontend: make Chat workflow run state and next actions explicit#2702

Open
AbigailDeng wants to merge 1 commit into
devfrom
feat/2026-07-10_chat-run-status-center
Open

Frontend: make Chat workflow run state and next actions explicit#2702
AbigailDeng wants to merge 1 commit into
devfrom
feat/2026-07-10_chat-run-status-center

Conversation

@AbigailDeng

Copy link
Copy Markdown
Contributor

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

  • Add a top-level Chat run status/action center derived from existing conversation and message runtime state.
  • Promote confirmation, operator action review, running step/tool context, stop semantics, and completed next-step guidance into that unified surface.
  • Remove the duplicate inline confirmation card so the main CTA appears in one place.
  • Add Chat-page tests for creating summaries, restored confirmation state, pending operator action state, and completed next-step guidance.
  • Add English and Chinese locale entries for the new status center copy.

Impacted Paths

  • apps/aevatar-console-web/src/pages/chat/index.tsx
  • apps/aevatar-console-web/src/pages/chat/index.test.tsx
  • apps/aevatar-console-web/src/locales/en-US.ts
  • apps/aevatar-console-web/src/locales/zh-CN.ts

Validation

Passed:

  • pnpm --dir apps/aevatar-console-web tsc
  • pnpm --dir apps/aevatar-console-web test:ui --runTestsByPath src/pages/chat/index.test.tsx --runInBand
  • pnpm --dir apps/aevatar-console-web build
  • git diff --check -- apps/aevatar-console-web
  • bash tools/ci/test_stability_guards.sh

Observed but not fixed in this PR:

  • pnpm --dir apps/aevatar-console-web test:ui still fails on existing non-Chat suites, including src/pages/teams/home.test.tsx, src/pages/scopes/invoke.test.tsx, and src/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

  • All edits are under apps/aevatar-console-web/**.
  • No backend, proto, docs, tools, CI, solution, root package, or agent files were changed.

Browser Verification

  • Attempted local browser verification against preview output.
  • Blocked by login redirect: opening http://localhost:5178/chat?scopeId=scope-a redirected to /login, so the authenticated Chat surface was not reachable in this environment.

FKST Provenance

  • Skill: aevatar-frontend-fkst
  • Issue: #2700
  • Worktree: /Users/abigaildeng/.codex/worktrees/fkst-issue-2700
  • Branch: feat/2026-07-10_chat-run-status-center
  • Commit: 1de88c63c

@AbigailDeng
AbigailDeng requested a review from potter-sun as a code owner July 10, 2026 07:19
@codecov

codecov Bot commented Jul 10, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.84%. Comparing base (88aa93b) to head (1de88c6).
⚠️ Report is 3 commits behind head on dev.

@@            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     
Flag Coverage Δ
ci 83.84% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1 file with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Frontend: make Chat workflow run state and next actions explicit

1 participant