All four tests were consistently failing (4/4 pre-push runs, not
intermittent) since commit 3640aec71 (2026-04-08, console.log →
expect conversion). The assertion-conversion landed without
verifying every new expect() against the current UI. SKIP_E2E=1
has masked them since the v1.0.6.2 hotfix.
Root cause investigation (4h timebox, 2026-04-18): actual cause
identified for each, fixes scoped in follow-up tasks. Not a race
condition / flake in the traditional sense — 3 of 4 are UI-drift
(selectors assume pre-v1.0.7 DOM shape), the 4th is a timing race
on expanded-player overlay that the inline comment documents
alongside the fix pattern (copy test 326's open-and-wait sequence).
Skip decisions made explicit rather than relying on SKIP_E2E=1:
* Each test.skip carries the full forensic note as an inline
comment — grep-able, code-review-able, impossible to lose.
* tests/e2e/SKIPPED_TESTS.md indexes the four with tracking
tickets (v107-e2e-01 through -04) and the unskip procedure.
* SKIP_E2E=1 stays as the env-var bypass but is no longer
required for the normal pre-push path — once this commit
lands, next pre-push runs the @critical suite with these four
skipped and the rest executing.
No v1.0.7 surface code touched. The four broken tests never
exercised marketplace / hyperswitch / stripe paths — they're all
player UI (3) and upload trigger (1), and v1.0.7 A-E commits all
land strictly in the money-movement surface.
Tracking tickets (#47-#50) include the fix hint for each, scoped
post-v1.0.7. SKIPPED_TESTS.md lists the unskip procedure: read the
inline note, implement the fix, run 100 local iterations green
before re-enabling.
This unblocks the v1.0.7-rc1 tag — the BLOCKER criterion
(investigation + PR-in-review before start of item F) is
satisfied: investigation done, root cause documented per test,
tickets opened with concrete fix hints.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
