Each translated page adds about 172 KiB to the Worker upload, so full ja coverage (#388) would exceed Cloudflare's 64 MiB Worker limit #395

Finding

The card thread measured this while it worked on #393 (PR #394). It found the problem on main's own code, not on #394's change.

• A build with every missing ja page filled in produces a 66,780 KiB Worker. Cloudflare's limit is 65,536 KiB.
• The Worker bundle fits the size budget CI step holds the upload to 61,440 KiB.
• Each added ja page grows the upload by about 172 KiB of page modules.
• The upload is about 55,400 KiB on main 09784e7, and about 56,600 KiB with fix(search): keep one locale index and read search text from build output (#393) #394's search data.

So the budget has room for about 28 more translated pages. Then, in the #388 batches:

• the re-land of docs(i18n): translate build/automation/ and build/interface/ into ja (#388, PR 2 of 7) #390's 11 pages fits,
• PR 3 (14 pages) fits,
• PR 4 does not.

Phase 3 of the locale plan, a second locale at full coverage, would need about 17 MB more.

CI goes red on the budget step before deploy, so this cannot take the live site down. It does block the locale plan.

Ask

Make the per-page cost of a translated page small enough that every planned locale fits under the budget with headroom. The target is ja fully covered plus at least one more full locale.

1. Measure where the 172 KiB per page goes. Look at the compiled MDX module, the highlighted code, the per-route server chunk, and any prerendered output that opennext also ships in the Worker.

2. Choose the cut from the measurement. Possible directions:

   • Serve the docs pages fully static, so that their modules do not need to be in the Worker.
   • Move highlighting cost out of the server bundle.
   • Share one module between a locale page and its English source.

   Say which one you chose and why, with before and after upload sizes.

3. Keep the Worker bundle fits the size budget step as the gate. Add a projection, for example a self-test or a summary line, that shows the KiB per page and the pages left before the budget. That way the next content batch can see its room before it is written.

Acceptance

• On the PR, a build with every missing ja page simulated, as copies of the English, fits under the 61,440 KiB budget, and the PR states the headroom for one more full locale.
• Every existing gate passes, including check-search-locales, check-search-heap from Search keeps every locale's index in one Worker isolate, so docs content growth pushes /api/search over the Worker's memory limit (503, deploy rolled back) #393, and the post-deploy smoke check after landing.
• No page changes how it renders. Check this with a browser test of one page per section in en and in ja.