Final pre-mainnet frontend readiness checklist

[Marvell69]

Description
Mirroring the smart contract repo's own pre-audit checklist concept, the frontend needs an analogous pre-mainnet readiness checklist consolidating the outcomes of this entire Wave's CI, security, accessibility, and testing work into a single sign-off document maintainers can use before flipping any mainnet-facing feature flags.

Requirements and context

• Create docs/pre-mainnet-checklist.md covering: all CI workflows green and pnpm-standardized (Issue 1), security headers in place (Issues 116–117), secret scanning clean (Issue 123), accessibility audit complete (Issues 89–96), feature flags for unshipped features confirmed off by default (Issue 113), Supabase/Resend production credentials properly scoped and rotated, and E2E suite passing against a mainnet-configured build
• This issue creates the checklist structure and cross-references the other tracking issues — it does not require all of them to already be complete, but should clearly show which are done vs. outstanding at time of writing

Suggested execution

git checkout -b docs/pre-mainnet-readiness-checklist

• Create the checklist, cross-referencing every relevant issue from this Wave
• Get maintainer review and keep it updated as dependent issues close

Example commit message
docs: create pre-mainnet frontend readiness checklist

[Abdulrasaq1515]

I want to create a pre-mainnet readiness checklist because the frontend needs an analogous pre-audit checklist consolidating CI, security, accessibility, and testing work into a single sign-off document. The checklist covers all CI workflows green, security headers in place, secret scanning clean, accessibility audit complete, feature flags off by default, production credentials properly scoped, and E2E suite passing.

Relevant experience:

Readiness checklists — wrote pre-launch checklists for 3 frontend projects; CI, security, accessibility, testing