Dashboard E2E: team-tab review-blocking test uses ambiguous locator #698

Summary

The Playwright test added in #695 (packages/codev/src/agent-farm/__tests__/e2e/team-tab.test.ts) fails on main under Playwright strict mode because its card selector matches multiple elements.

Failing test

Team tab: review-blocking rendering (spec 694) › renders both-direction sentences with a mocked /api/team response

Workflow run: https://github.com/cluesmith/codev/actions/runs/24825687747

Root cause

const amrCard = page.locator('.team-member-card', { hasText: 'Amr' });
await expect(amrCard).toContainText("You're waiting for");

hasText: 'Amr' matches two cards:

1. Amr's actual card (member name is "Amr")
2. Waleed's card — which now contains the substring "Amr" inside the new review-blocking sentence ("Amr is waiting for you to review chore: consolidate local-install flow into a single shell script #688").

The feature this PR shipped broke its own test: review-blocking text legitimately mentions the other person's name, so filtering cards by name substring is no longer unique.

Same issue applies to waleedCard.

Suggested fix

Use a more specific locator that matches the card by its identity rather than any text inside it:

• Filter by the @amr / @waleed handle (rendered in .team-member-handle or similar), or
• Use page.locator('.team-member-card').filter({ has: page.locator('h3', { hasText: 'Amr' }) }) or equivalent on whatever element renders the member's name as a heading.

Either makes the assertion robust to future content that may mention other members' names.

Impact

Blocks the scheduled Dashboard E2E workflow on main. The PR's own CI passed because the Dashboard E2E workflow runs on schedule, not on push/PR.