Summary
The team page currently shows only counts (e.g., "3 issues", "2 PRs") for each member. The backend already fetches full issue/PR titles and URLs via GraphQL, but the frontend discards this data and renders only counts.
Requirements
1. Expanded member cards
Show actual issue/PR titles under each member instead of just counts:
- Working on section: list assigned issue titles (clickable, linking to GitHub)
- Open PRs section: list open PR titles (clickable)
- Recent activity summary: merged/closed counts with "last 7d" label (keep existing)
2. Combined activity feed
Add a third section below Messages — a unified timeline of recent activity across all members:
- Show merged PRs and closed issues from the last 7 days
- Each entry: date, @author, action (merged/closed), #number, title
- Sorted reverse chronologically
- Clickable issue/PR numbers linking to GitHub
Constraints
- Frontend-only change — no backend modifications needed
- All data is already available in
TeamMemberGitHubData (assignedIssues, openPRs, recentActivity)
- Files to modify:
TeamView.tsx (component) and index.css (styles)
- Keep existing member card info (name, role, GitHub handle)
Scope
- ~200 LOC frontend change
- ASPIR protocol appropriate (low risk, no architectural decisions)
Summary
The team page currently shows only counts (e.g., "3 issues", "2 PRs") for each member. The backend already fetches full issue/PR titles and URLs via GraphQL, but the frontend discards this data and renders only counts.
Requirements
1. Expanded member cards
Show actual issue/PR titles under each member instead of just counts:
2. Combined activity feed
Add a third section below Messages — a unified timeline of recent activity across all members:
Constraints
TeamMemberGitHubData(assignedIssues, openPRs, recentActivity)TeamView.tsx(component) andindex.css(styles)Scope