test: add Explorer production smoke coverage

[paulbalaji]

What

• add a Playwright production-browser smoke test for the Explorer homepage, chain picker, and message timeline
• run it against the built Next app in the existing CI build job
• verify hydration, live Latest Messages data, POST GraphQL transport, and app/widget layout

Why

The dependency upgrade passed build, typecheck, lint, unit tests, and Vercel deployment while the deployed app had three user-visible regressions:

• a Zustand 5 render loop during hydration
• urql 5 GET requests rejected by the GraphQL edge
• Tailwind 4 utilities losing to the unlayered widget preflight

This test exercises the actual browser/runtime/data path that those checks missed.

Assertions

• search UI hydrates without uncaught page errors or the app error boundary
• at least one live message row renders
• GraphQL queries use POST, not GET
• header/footer logos and search input keep their compact production heights
• Origin, Destination, Time, and Status controls remain compact
• the Origin chain picker renders its search, controls, and chain rows as the intended grids
• a delivered message renders four timeline bars and four correctly positioned stage icons
• Jest excludes the Playwright-only smoke directory

Verification

• pnpm install --frozen-lockfile
• pnpm build
• pnpm exec jest --runInBand — 14 suites / 129 tests pass
• pnpm test:smoke — 1 passed

Follows the merged runtime/style hotfix #343. This coverage is the gate for the separate Tailwind 4 migration follow-up.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
hyperlane-explorer	Ready	Preview	Aug 10, 2026 10:55am

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​playwright/​test@​1.62.1

View full report

[coderabbitai]

Warning

Review limit reached

@paulbalaji, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 15 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 814dc658-348d-4e69-9293-485fac62876d

📥 Commits

Reviewing files that changed from the base of the PR and between cc4006b and d762650.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (6)

• .github/workflows/ci.yml
• .gitignore
• jest.config.js
• package.json
• playwright.config.ts
• tests/smoke/homepage.spec.ts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[paulbalaji]

Exact-head verification complete at d762650:

• all CI checks pass, including the production build + Playwright smoke job
• local smoke covers hydration, live messages, POST transport, homepage controls, the chain picker, and the message timeline
• chore: upgrade Tailwind to 4 #345 now runs this same smoke suite as its stacked Tailwind 4 migration gate