bug: E2E flake — "owner can re-invite and invited user can accept" strict mode violation

[zacharias-ona]

Description

The E2E test members.spec.ts:139 ("owner can re-invite and invited user can accept") fails with a strict mode violation because locator('text=E2E Member') resolves to 2 elements instead of 1. This indicates duplicate member entries appear in the members list after a re-invite + accept flow.

Detected during post-merge verification of PR #214, but the failure is unrelated to that PR's changes (slash menu navigation). This is a pre-existing issue in the member management flow.

Acceptance Criteria

• The re-invite and accept flow does not produce duplicate member entries
• The E2E test owner can re-invite and invited user can accept passes reliably
• The dependent tests (role change, member removal) that were skipped due to this failure also pass
• pnpm lint && pnpm typecheck && pnpm test pass

Technical Notes

• Failure: locator('text=E2E Member') resolves to 2 elements (strict mode violation) at e2e/members.spec.ts:194
• Root cause: After re-inviting and accepting, the member appears twice in the list — likely a duplicate row in the database or a UI rendering issue
• Impact: 3 downstream tests are skipped because they depend on this test
• Affected route: /{workspace}/settings (members tab)
• PR that surfaced the regression: fix(editor): stabilize slash menu arrow key navigation (#205) #214 (not the cause)