Follow-up by 2026-08-31: finish Cypress e2e ourselves if #984 stalls

[northdpole]

Reminder (due end of August 2026)

If #984 is still not mergeable by 2026-08-31, do the remaining work ourselves (or close #984 and land an equivalent PR).

Context

• Tracking issue: E2E: migrate frontend to Cypress (consolidate #729 + #774); keep Python Playwright #967
• Active PR: fix(e2e): consolidate frontend E2E to Cypress and restore CI (#967) #984 (CHANGES_REQUESTED, currently conflicting with main)
• Author: @DevHusnainAi

Outstanding from maintainer review (2026-07-22)

Blocking

1. Replace live upstream_sync in make e2e-db with a minimal checked-in fixture seed
2. Drop e2e CI timeout (~45m → ~15m) once sync is gone
3. Keep SQLite create_all for e2e (do not switch back to migrate-upgrade)
4. Stronger CRE filter assertions (links content, not just chrome)
5. Stronger search assertions (data-bearing results)

Also: rebase onto main, address soft TODOs as practical, close #774 as superseded when done.

Done when

• Frontend Cypress e2e CI job is green on main without hitting opencre.org for seed data
• E2E: migrate frontend to Cypress (consolidate #729 + #774); keep Python Playwright #967 can be closed

[DevHusnainAi]

@northdpole Understood and sorry this was my first time I wasn't but now all things are clear and I will close it soon.

Thanks for guidance 🙏.

[northdpole]

Closing — we should not use GitHub issues as personal deadline reminders. Tracking stays on #967 / #984; Aug 31 follow-up will be a calendar/chat reminder instead of a fallback ticket.