Repository navigation
[PR] docs: add Japanese versions of repository documentation (#6072) - #6076
Conversation
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.9427-pr.6076.8b67d60This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr6076.tgz
npm install -g packageInstall instructions are refreshed on each push. |
(ai: vllm-qwen/qwen3.8-27b) 查重: 不重复。Scanned open [PR] rows (78 total): this thread (GitHub PR #6076) is the only one targeting the Japanese-docs batch under #6072 — no parallel second PR exists, so my review fixes went onto this same branch (one PR per thread). 标签: scope/docs + p3(纯文档翻译交付,无运行时影响,可发现性层级);原有 pr 标签保留。 Review — PR #6076 (batch 1: Identity & protocol JA translations)Verified live just now (branch
Two small fixes pushed to the branch during review (trivially safe, each its own labeled commit):
八问
判定:可合。技术面无阻塞(base 最新、diff 干净、保真度机械验证通过、CI 绿),等你批准合并即可。剩余批次(message-identity/session-identity → clients/technical-notes/architecture → engineering & ops → 生成的 configuration)按计划以后续 commit 落到同一分支(一个线程一个 PR)。 |
ranxianglei
left a comment
There was a problem hiding this comment.
(ai: vllm-qwen/qwen3.8-27b)
Verdict: APPROVE — docs-only PR; verified faithful and complete against all four EN sources; four small fidelity nits found, all resolved on the branch during review (two fixed in parallel by the author, two by me on top of theirs).
Correctness. Read all four EN sources in full and cross-checked every section, bullet, table row, code span and issue reference against the JA text:
- Heading structure mirrors 1:1 in all four pairs; issue-ref sets (#NNNN) identical in all four.
- Structural counts equal: session-identity-resolution 15 bullets / 9 numbered / 6 table rows; identity-channels 6 bullets / 19 table rows; msgid-infrastructure 4 bullets / 22 table rows; opencode-responses-websocket 10 bullets. (msgid-infrastructure showed 9 EN vs 8 JA numbered items — that gap IS finding #2 below, not dropped content.)
- Line-count gaps (EN 150→JA 62 etc.) are fully explained by EN soft-wrap vs JA single-line paragraphs; content is complete.
- Fenced code blocks now byte-identical to EN (verified by diff after the fix).
.ja.mdnaming follows the README.ja.md precedent (#6004); absence of a top-of-file language-toggle line on content pages matches convention (only configuration.md has one); both index files register the new pages and surface the previously-unlinked README.ja.md.
Tests / CI guards. No test surface exists or is needed for markdown. The lanes that could care are unaffected: architecture-docs scans only the docs/architecture/ hub + pages; docs-sync diffs only the generated config docs; docs-coverage is config-reference coverage. All green on head 2e59aa8; re-running after my two doc-only commits.
Risks. Zero: no code, config, wire, persistence, kernel, or version touched. No behavior drift to disclose.
Fixes made on this branch during review:
已顺手修:msgid-infrastructure.ja.md §8 item 5 lost its list rendering ('5.' had no trailing space → GitHub renders it as a plain paragraph, not list item 5) + commit b11fce2
已顺手修:opencode-responses-websocket.ja.md dropped the registration name — EN 'registered as responsesCodec in a codec table' became nameless 'コーデックテーブルに登録される' + commit fa31da6
(Parent commits 7fc8684 fence diagram restored byte-exact to EN, and 2554e48 index.zh-CN README row labels de-crossed, were pushed in parallel by the author while this review was running — verified equivalent, my duplicate attempts dropped in favor of theirs, which matches sibling-row house style better.)
结构化八问(中文)
- 是什么问题:不是缺陷修复——为身份与协议四篇文档补日语译本(#6072 全量日语文档化第 1 批),并在两个索引中登记新页、顺带链接此前未链的 README.ja.md。
- 什么原因导致的:不涉及(新增翻译,无根因)。
- 影响范围与严重程度:仅文档可读面;对现有用户零行为影响。
- 怎么修复的:逐篇对照 EN 原文做无损镜像(标题/列表/表格/代码块/issue 引用逐项核对);命名沿用 README.ja.md 先例;审查中发现的 4 处保真度小疵当场修掉(围栏图字节对齐、列表项缺空格、注册名丢失、索引标签错位——后两处前两个由作者并行提交等价修复,本审核采纳作者版本)。
- 是否有回归问题:无——纯 .md 新增 + 索引行;architecture-docs / docs-sync / docs-coverage 三个相关 CI 门均不受影响且绿;未触碰任何代码/配置/线协议/持久化格式/版本号。
- 是否破坏缓存:不涉及。
- 是否改了设计方向:不涉及。
- 是否引入了新的配置:不涉及。
判定:可合(APPROVE)。最终 head fa31da6 的 CI 复跑中(两个新增 commit 均为纯 markdown,零代码路径)。
[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b) Review lane done: PR #6076 (Japanese .ja.md translations — identity & protocol section, batch 1 of #6072) reviewed end-to-end → APPROVE / 可合. What was checked. Read all four EN sources in full and cross-checked every JA file section-by-section: headings mirror 1:1, bullets/tables/numbered items count equal (15+9+6 / 6+19 / 4+22+9 / 10), issue-ref sets identical in all four pairs, fenced code blocks byte-identical after fix; line-count gaps fully explained by EN soft-wrap vs JA single-line paragraphs. Naming follows the README.ja.md precedent (#6004); JA pages correctly omit any top-of-file toggle line (only configuration.md has one). Docs-only diff (6 files, +234/−10) — no code/config/wire/persistence/version touched; architecture-docs, docs-sync, docs-coverage lanes unaffected, all green on head 2e59aa8, re-running on final head fa31da6. Findings — all closed, none parked. Four small fidelity defects found during review:
GitHub review posted as a review-comment with full verdict (APPROVE event refused — this account is the PR author): #6076 (review) · One-line report filed on #4599. Awaiting owner merge. 结构化八问(中文)
判定:可合(APPROVE),待 owner 合并。 |
(ai: vllm-qwen/qwen3.8-27b) Status update — the branch moved while I was reviewing; refreshed everything against the new head. My previous comment cited head What landed after my last comment:
Batch-2 verification (me, just now): extended the same mechanical fidelity check to all 6 EN↔JA pairs — fenced blocks byte-identical, inline-code span multisets identical (after stripping fences and normalizing legitimate multi-line spans), issue-ref sets identical, heading level-sequence identical (1:1 heading correspondence in both new pages). Index registration verified against both files. Two residual nits found, fixed as labeled commits
Full fidelity re-run after those fixes: all 6 pairs clean. CI at head 八问(增量更新,相对上一条回复)
判定:维持可合——等主 CI 出队跑完(预计很快)+ owner 批准合并。剩余批次(clients/technical-notes/architecture → engineering & ops → 生成的 configuration)继续按「一个线程一个 PR」落到本分支。 |
ranxianglei
left a comment
There was a problem hiding this comment.
(ai: vllm-qwen/qwen3.8-27b)
Verdict: APPROVE — posted as a comment because this account cannot approve its own PR (same as round 1).
Round-2 re-review at final head 02c4f7b41c (branch moved from f1c13181f5 while I was reviewing: author commits 11f3cc787f, 784f137e34, 9ceb10f76c + two reviewer fixes below). Full PR at merge-base 541cf260c4: 9 files, all under docs/, 938+/16- — seven new .ja.md translations plus index rows in both index files. Docs-only; no code/config/wire/persistence surface touched; branch is behind master with zero file overlap -> clean merge.
Faithfulness verified section-by-section against the EN sources:
message-identity.ja.md(419 L) vs.md(432 L): headings 1:1 (18), bullets 19/19, table lines 21/21, issue-ref sets identical, fenced diagram byte-identical. All specifics carried: #242 66-char id vs 64-char cap, #2396 (~66,525 tokens re-entered at 558,541/562,549 vs the 500,000-token window), SHAPE_MASS_MIN / simhash <= 8 gate, 16384-anchor cap, tests/identity-proof.test.ts matrix, #3756/#3751 mechanics.session-identity.ja.md(255 L) vs EN (268 L): headings 1:1 (19 incl. ###), bullets 21/21, numbered items 3/3, table lines 19/19, issue refs identical. Measurement table (9,367 full-prefix / 2,106 new / 142 fork lineage / 0 tail-window), TRUNCATION_LINEAGE_WINDOW = 8 / MIN_FORK_PREFIX = 3, wire-neutral projection rules, live evidence (45 KB file, ~13.5k tokens saved, 97% cache hit within two rounds) all present.README.ja.md(24 L) vsREADME.md: intro / catalog blockquote / 4-row section table (identical link sets) / 5 rules / AGENTS pointer — faithful.- Index rows: this round only touches the README row (
/ [日本語](README.ja.md)appended in each file); pattern matches the sibling rows exactly.
Author's proactive fixes — all correct, adopted:
11f3cc787f: si.ja.md code spanTRUNCATION_LINEAGE_WINDOW = 8was split mid-token across a line break inside backticks (CommonMark renders that as an inserted space); re-wrapped, no content change. Real rendering defect, fixed right.784f137e34: mi.ja.md heading(#3641)mixed-width parens ->(#3641). Identical to my queued finding; the author got there first.
已顺手修:message-identity.ja.md summary line render join(rollout gate) mixed-width parens -> (rollout gate) + commit 424a7e9489
已顺手修:README.ja.md 「落地ページ」(Chinese calque of "landing page") -> 「ランディングページ」(standard term, matches the file's katakana style) + commit 02c4f7b41c
Tests/CI: docs-only — no test surface exists for this diff. At head 9ceb10f76c the gate lanes are already green (static-gates, mysql-contract, test-import-graph, config-surface-guard, ...); the test shards were still running when I posted and cannot be affected by a docs-only diff.
Risk: none. No behavior drift, nothing to disclose 旧值->新值.
结构化八问
- 是什么问题:无缺陷——本 PR 是纯文档新增(message-identity / session-identity / docs 落地页的日文翻译 + 两个 index 的行);本轮审核对象是作者在我首轮审核后新推的三个 commit(含作者自修的一处渲染缺陷)。
- 什么原因导致的:不涉及(非 bug 修复类 PR)。
- 影响范围与严重程度:仅文档可读性面——为日文读者新增三个文档入口;不触碰任何代码、配置、协议、持久化路径。
- 怎么修复的:不适用(审核 + 两处顺手小修:全角括号宽度不一致 x1、日文用词校准 x1)。
- 是否有回归问题:审过的既有行为——两个 index 文件的行格式与既有兄弟行模式完全一致;全部 EN 源文件零改动;CI guard(architecture-docs / docs-sync / docs-coverage)的扫描范围均不覆盖顶层 .ja.md。无回归。
- 是否破坏缓存:不涉及。
- 是否改了设计方向:不涉及。
- 是否引入了新的配置:不涉及。
判定:可合。
[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b) Round 2 review 完成: GitHub PR #6076 APPROVE — final head
判定: 可合。GitHub 审核评论: #6076 (review) |
(ai: vllm-qwen/qwen3.8-27b) Red CI cleared — no code change needed. The single failing job was a transient flake, unrelated to this docs-only PR. What I did this run (verified live):
No commits, no pushes, zero branch changes. Nothing was merged or modified. 八问(CI 修复结论)
判定:CI 侧已清,该文档 PR 从 CI 角度可合并。 附注: |
438fbe8 to
699a6a4
Compare
|
Final batch landed — the PR now covers the full agreed scope (README +
All translations were machine-translated (local qwen3.8-27b) then audited structurally: code fences byte-identical, table row counts, Body now flips to |
(ai: vllm-qwen/qwen3.8-27b) CI on the new head ( What I found and did (verified live):
So the only remaining gates on this PR are the human ones you named: locals proofreading the prose, then merge. I did not proofread the translations — naturalness is the human part you called out, and a structural audit can't guarantee it. 八问(CI 结论)
判定:新 head 的 CI 已全绿,该文档 PR 从 CI 角度可合并;剩余门禁是你点名的人工校对(译文自然度)与合并。 附注:该 Windows teardown 抖动在 3s/6s/10s/20s 预算下仍偶发,属 master 级 CI 稳健性问题(已在 #4599),不适合塞进本纯文档 PR;若要根治(让该用例不依赖墙钟预算)应单独立项。 |
[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b) CI on the new head
Remaining gates are the human ones you named: locals proofreading the prose, then merge. I did not proofread the translations (naturalness is the human part). 八问(CI 结论)
判定:新 head 的 CI 已全绿,该文档 PR 从 CI 角度可合并;剩余门禁是人工校对(译文自然度)与合并。 |
…l pointed at the Chinese file)
…odec' registration name
…an on one line The constant was wrapped mid-token across a line break inside its code span; CommonMark renders that newline as a space, so the identifier displayed as 'TRUNCATION_LINEAGE_ WINDOW = 8' instead of 'TRUNCATION_LINEAGE_WINDOW = 8'. Re-wrapped the paragraph; no content change.
Faithful complete mirror of docs/README.md; registers the ja link on the directory-landing row of both index files.
…ate)' summary line
ja pages reuse the EN diagrams (svg+png); hub ledger locked to EN by the extended check-architecture-docs guard.
…upport (#6072) - gen-config-docs.mjs: ja seed field (desc_ja, required), ja param-ref and env-map blocks written to docs/configuration.ja.md; EN/ZH/main.js/html output byte-identical - all 8 config-reference seeds: 339 desc_ja entries - check-architecture-docs.mjs: ja hub/module-page rules (ledger parity with EN hub, EN-diagram reuse) - ci.yml docs-sync lane now drift-checks docs/configuration.ja.md too - configuration.md / configuration.zh-CN.md: three-language switch line
699a6a4 to
db2e1de
Compare
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.1182-master.dd0ef22 # this exact build
npm install -g billion-context@master # always the newest merged build
|
…landed on master during rebase)
Adds Japanese (
ja) translations of the repository documentation, per #6072 ("All repository documentation is available in Japanese"). Single long-lived PR for the issue (owner: one PR, don't split); each section lands as its own commit on this branch.Convention
.ja.md(matches the existing rootREADME.ja.mdfrom [PR] docs: add Japanese README (#6000) #6004); existing Chinese docs keep.zh-CN..zh-CNtwins.configuration.mdcarries one); discovery is via the index rows indocs/index.md+docs/index.zh-CN.md.Scope (owner-ruled 2026-11-10)
README +
docs/only.AGENTS.mdis explicitly excluded (it's for LLMs, no Japanese needed). Root operational files outside "readme+docs" —CHANGELOG.md,reference/*— are out of scope. Four deliberately single-languagedocs/files with no Chinese twin stay English-only by default:lifecycle,auto-merge-guardrails,unified-loop-spec,plugin-protocol. Say the word if any of those should be localized too.Progress (complete 2026-11-13)
opencode-responses-websocket,session-identity-resolution,identity-channels,msgid-infrastructure,message-identity,session-identitydocs/README.ja.mddocs/technical-notes.ja.md(+ rootTECHNICAL-NOTES.ja.mdredirect stub)docs/architecture.ja.md+docs/architecture/*.ja.md;tools/check-architecture-docs.mjsnow enforces the ja pages (ledger parity with the EN hub, EN-diagram reuse); diagrams reuse the en SVGs with a one-line notedocs/configuration.ja.mdviatools/gen-config-docs.mjs(339desc_jaseed entries; CI docs-sync lane drift-checks the ja file too)[日本語]links on every row indocs/index.md+docs/index.zh-CN.md; root redirect stubs (CLIENTS/CONFIGURATION/MESSAGE-IDENTITY/SESSION-IDENTITY/TECHNICAL-NOTES.ja.md)Closes #6072