Direct answer: On 2026-07-20 we confirmed Japanese tool labels stay aligned with the English/Chinese catalog, and blog/news publishing continues to require complete en / zh / ja bodies before an article is listed publicly.
Developers switching locale mid-debug should not lose the mental model of a tool because its title falls back to English. The UI copy layer already resolves Japanese titles and subgroup labels when locale === "ja". This update documents the operational expectation: catalog labels and content bodies move together.
On the publishing side, news and blog markdown keep the same markers (<!-- locale: en|zh|ja -->) and date: "YYYY-MM-DD". Incomplete language blocks stay out of the public list so Japanese readers get the same debugging steps—not a title-only stub. Practical guides still focus on deterministic utilities (JSON, webhooks, hashes, encoding), not generative fluff.
Switch to 日本語 in the language control to verify tool names, then open Blog/News for matching bodies. Wording fixes: sapsap@qq.com.