chore(e2e): silence 5 broken specs to restore CI signal (PP-5ra)

[timothyfroehlich]

Why

Main CI has been red for several days due to 5 known-broken E2E specs. Every in-flight PR inherits these failures and looks broken even when its own diff is clean — making CI signal untrustworthy and slowing down all parallel work.

This PR silences the 5 specs via test.fixme(true, "REASON") so:

• Main goes green immediately (~10 min after merge)
• PR CI signal becomes trustworthy again
• The 5 broken specs are explicitly counted and tracked, not implicitly subtracted in everyone's head

Why test.fixme() and not test.skip() or test.fail()?

test.fixme() marks the test as broken and skips execution. Each call carries a string reason that lives in source code right next to the test, so the bug is visible to anyone reading the spec.

test.skip() would also skip but loses the "this is broken, fix me" semantic. fixme() is more honest about intent.

test.fail() would run the test and pass CI when it fails, fail CI when it passes — but two of our five (PP-jsh, PP-v7g) are flaky, not deterministically broken. They sometimes pass and sometimes time out under CI load. test.fail() would fire false-positive failures on the runs where they happened to pass. The other three (PP-q9r, PP-e20, PP-49m) are deterministically broken right now but the cause might shift, so we'd rather not couple to "must always fail."

test.fixme() is the right tool for "we know these are broken/flaky, track them explicitly, restore them by removing the fixme as part of the bug-fix PR."

Trade-off accepted

With test.fixme(), if someone accidentally fixes a bug elsewhere that resolves one of these specs, CI won't notice — the test stays skipped. Mitigation: the binding rule below + the grep audit (rg 'test\.fixme\(true, "PP-' e2e/) make the count explicit and visible. Each fixme is removed by the PR that fixes its bead, at which point the test runs again on real CI.

Silenced specs (10 fixme calls across 5 files)

Spec	Bead	Reason
email-and-notifications.spec.ts (password reset flow)	[PP-q9r]	pkce verify URL doesn't redirect to /reset-password; needs iter 3
oauth-connected-accounts.spec.ts:29,63	[PP-e20]	Discord OAuth not configured in test env; mock-only fix groomed
machine-details-extended.spec.ts (4 tests using logout())	[PP-jsh]	Radix DropdownMenu portal mount timing; awaiting PP-awg verification
status-overhaul.spec.ts:21	[PP-v7g]	Radix Select portal mount timing; awaiting PP-awg verification
issues-crud-extended.spec.ts:43,60	[PP-49m]	Unwatch strict-mode violation; fix folded into #1270

🚨 BINDING RULE

Feature PRs do not merge while any test.fixme(true, "PP-...") exists in the codebase.

Each fixme is removed by the PR that fixes its bead. The current count is the explicit CI debt — track it down to zero before resuming feature work.

To audit:

rg 'test\.fixme\(true, "PP-' e2e/

Test plan

• pnpm run check passes locally
• Each fixme lives inside the correct test body
• CI Gate passes on this PR (the 5 fixmes mean E2E Full Tests skips them rather than fails)
• Main goes green within 1 run after this lands

Tracking

• Meta: PP-5ra
• Per-spec: PP-q9r, PP-e20, PP-jsh, PP-v7g, PP-49m

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
pin-point	Ready	Preview, Comment	May 5, 2026 8:04pm

[supabase]

This pull request has been ignored for the connected project udhesuizjsgxfeotqybn due to reaching the limit of concurrent preview branches.
Go to Project Integrations Settings ↗︎ if you wish to update this limit.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[Copilot]

Pull request overview

This PR restores CI signal by marking 5 known-broken Playwright E2E tests as fixme, preventing them from failing the full E2E suite while keeping the debt visible in reports and source.

Changes:

• Mark the Status Overhaul badge verification E2E as test.fixme(...) due to Radix Select portal timing flake.
• Mark Discord OAuth redirect E2Es as test.fixme(...) pending a mock-only approach in CI.
• Mark several machine details + watch/unwatch E2Es as test.fixme(...) due to portal timing / strict-mode selector issues.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
e2e/full/status-overhaul.spec.ts	Adds test.fixme(true, ...) to silence a flaky Radix Select-driven scenario.
e2e/full/oauth-connected-accounts.spec.ts	Adds test.fixme(true, ...) to silence Discord OAuth redirect tests in CI.
e2e/full/machine-details-extended.spec.ts	Adds test.fixme(true, ...) to silence tests impacted by Radix DropdownMenu portal timing.
e2e/full/issues-crud-extended.spec.ts	Adds test.fixme(true, ...) to silence strict-mode Unwatch button selector failures.
e2e/full/email-and-notifications.spec.ts	Adds test.fixme(true, ...) to silence the password-reset journey test pending flow correction.