feat(teams): show per-member task status in team progress message - #255
Open
BlueX888 wants to merge 1 commit into
Open
feat(teams): show per-member task status in team progress message#255BlueX888 wants to merge 1 commit into
BlueX888 wants to merge 1 commit into
Conversation
Addresses OpenBMB#229. While a team run is collecting or synthesizing, the TL session progress bubble now lists each task with its assignee name and a human-readable status (incl. 已提交待验收 and 等待人工补充信息), and team_progress metadata carries a structured tasks array for future UI use. Session summaries keep only the headline line. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
Addresses #229.
What: While a team run is collecting or synthesizing, the TL-session progress bubble now lists every task with its assignee name and a human-readable status — including
已提交，待验收(review) and等待人工补充信息(escalated withneeds_input) — instead of only the aggregate已收到 X/Y 项成员回复. Theteam_progressmetadata additionally carries a structuredtasksarray for future frontend use, and session summaries keep only the headline line.Why: #229 reports that the delivery manager cannot tell from the team session whether an @-mentioned member finished or is stuck in review/escalated. This keeps the locked TL-mediated design (no direct @ routing, no extra messages) while closing the visibility gap.
How verified:
backend/tests/test_teams_api.py43/43 passed, including a new regression test for the review/needs-input labels and the summary headline. The 11 failures in the full backend suite (channel/feishu migration tests) and the 10 ruff findings in touched files were confirmed pre-existing on cleanmainvia stash — this change adds none. Backend-only; no schema change; frontendteam_progressconsumers only readphase/status_text, both unchanged in shape.🤖 Generated with Claude Code