Thanks for spotting this issue and submitting PR #2. Your diagnosis is very helpful!
The bug has now been fixed and deployed. My AI tool didn’t merge the PR directly because it also included broader generated-data changes. Instead, the AI tool took the safer route: applying the parts that preserve manually reviewed overviews and enforce translation-length limits, then adding per-proposal error isolation and browser-side error monitoring.
The landing now loads normally, and translation failures can no longer bring down the page.
Thank you for the PR#3 and the clear explanation! I’ve merged it.
I also added a small follow-up: an automated test now keeps the /live/* proxy rules in next.config.ts and vercel.jsonsynchronized, and the code/PR notes now clarify the media-type headers required by the CKB Explorer balance endpoint.
Everything passed the tests and build, and the updated site has been deployed successfully. Really appreciate your contribution!