feat: global error boundary for safer recovery

[jbeard4]

Summary

• add a global error boundary and route-level fallbacks for the map, list, and static content segments
• document the new recovery UI and how to reproduce DOMException crashes locally
• introduce Google Translate DOM simulators plus unit and e2e scaffolding to exercise the issue in CI

Testing

• npm run test:unit

---

https://chatgpt.com/codex/tasks/task_e_68f1c88bb2148327ab96207e5c725e5d

[chatgpt-codex-connector]

💡 Codex Review

yourpeer.nyc/package-lock.json

Lines 1 to 7 in 0872af5

	"@playwright/test": "^1.51.1",
	"@testing-library/dom": "^10.4.1",
	"@testing-library/jest-dom": "^6.6.3",
	"@testing-library/react": "^16.1.0",
	"jsdom": "^27.0.0",
	"typescript": "^5.7.2",
	"vitest": "^2.1.8"

Restore valid package-lock.json structure

The new package-lock.json no longer starts with the root object – the file now begins at dependency entries ("@playwright/test": …) and is missing the opening braces and metadata (name, lockfileVersion, etc.). This leaves the lock file unparsable (node -p "require('./package-lock.json')" throws a SyntaxError: Unexpected non-whitespace character). A corrupted lock file will cause npm install or any CI workflow that relies on the lock to fail. Please regenerate the lock file so that it is valid JSON.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting

• @codex fix this CI failure
• @codex address that feedback