chore(web/docs): pre-launch polish — Lighthouse, a11y, spelling/grammar, landing + docs cleanup

[EricAndrechek]

Area: website · docs — pre-launch QA · from Eric's notes

A bundle of public-facing quality checks to land before flipping public. Track here; split out if any item grows:

• Lighthouse pass (perf / SEO / best-practices) on the docs site + landing.
• Accessibility audit (WCAG basics: contrast, alt text, keyboard nav, semantics).
• AI-assisted accessibility review as a second pass.
• Spelling + grammar sweep across site + docs.
• Landing-page refactor.
• Docs cleanup (post-feat(docs): rebuild site with wavehouse logo and design tokens #142 redesign / after fix(docs): final passes on docs before publish #193's pass lands).

Scope: public-facing polish only — front-door credibility for the OSS launch.

Related: docs final passes #193; docs deploy (closed #148).

---

From Eric's notes scratchpad; triaged 2026-06-04.

[coderabbitai]

🔗 Related PRs

#142 - feat(docs): rebuild site with clickwave logo and design tokens [merged]
#187 - docs: prep docs for publishing [merged]
#307 - fix(docs): fix homepage NO_LCP while keeping the hero fade-in [closed]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!