[dinahmaccodes]

Summary

This PR addresses four GitHub issues across testing, CI/CD, and documentation:

1. Testing: run the browser journey against a production frontend build #111: Added production-mode E2E test configuration that builds once and tests against the built artifact using next start, instead of starting the dev server. CI now runs test:e2e:prod after building.

2. CI: retain Playwright traces and reports when browser tests fail #110: Configured Playwright to upload test traces and HTML reports on failure, with unique artifact names to prevent collisions across matrix jobs and a 7-day retention period.

3. Docs: add a Testnet reset recovery runbook #123: Created TESTNET_RESET_RECOVERY.md runbook documenting network reset symptoms, recovery procedures, and offline report preservation.

4. Docs: explain report fields with a sanitized annotated example #120: Added comprehensive report field reference to API.md with a complete annotated JSON example covering all fields (provenance, timeline, steps, assertions, summary, and optional error details).

Test plan

• Verify npm run test:e2e:prod builds and tests the production bundle
• Confirm failed test artifacts upload to GitHub Actions with proper retention
• Review the reset recovery runbook for clarity and accuracy
• Validate the annotated report example parses as JSON and matches RunReport schema

Closes #111
Closes #110
Closes #123
Closes #120

[vercel]

@dinahmaccodes is attempting to deploy a commit to the Favour Chigozirim's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

@dinahmaccodes Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits