[E2E] Seeded admin@breeze.local is a Partner Admin with force_mfa=true — global-setup bounces to /auth/mfa/setup and every spec dies on a wt-stack

[ToddHebebrand]

Description

On a worktree-stack / wt-stack stack, Playwright global-setup.ts logs in as the seeded admin@breeze.local. That user is a Partner Admin whose role carries force_mfa = true (#4491), so login redirects to /auth/mfa/setup and the shared storage state is never written — every spec fails before it starts. Two fixer sessions on 2026-09-08 (PR #5261, PR #5260) each had to run update roles set force_mfa = false against the throwaway DB by hand.

Proposed Fix

Either seed a dedicated e2e login user whose role does not force MFA (preferred — keeps the Partner Admin posture intact), or have e2e-tests/seed-fixtures.sql / the stack seed clear force_mfa for the e2e role only, or complete MFA enrolment in global-setup.ts with a seeded TOTP secret. Document the choice in e2e-tests/README.md.

Affected Files

• e2e-tests/global-setup.ts
• e2e-tests/seed-fixtures.sql (or the seed the worktree-stack skill applies)
• e2e-tests/README.md

Reported By

Fixer sessions on PRs #5260 and #5261, 2026-09-08.