Repository navigation
[PR] docs: permit root README.<locale>.md community translations (#6000) - #6001
Conversation
…n LIVE_FILES Converged master-red fix (sentinel ci-fixes lane): #5989 merged the spawning suite without registering it, so the #1248 SPAWN_RE tripwire kills all 11 core-matrix test shards before any test runs on every PR head. Hunk is byte-identical to open PR #5990 (which carries the same registration plus a test-tolerance change to master).
Carve out a bounded exception to the 'repo root keeps only four entry files' Documentation Layout rule: the root may also hold recognized community-maintained README translations (README.<locale>.md), e.g. README.ja.md (owner-approved 2026-11-09, #6000). The four core entry files stay locked; new non-translation docs still go in docs/. Amended consistently across all five locations (AGENTS.md, docs/index{,.zh-CN}.md, docs/README{,.zh-CN}.md).
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.8747-pr.6001.ea0c184This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr6001.tgz
npm install -g packageInstall instructions are refreshed on each push. |
(ai: vllm-qwen/qwen3.8-27b) 查重: 不重复 — 本线程就是规则口子 PR #6001 本身;检索 open+closed 无并行的同类规则修订 PR,上游需求为 #6000(本 PR 为其前置,Refs 而非 Closes)。 标签: pr(既有) + p3 + scope/docs — 纯文档规范修订,无代码/wire/config 影响。 Live 状态核验(刚查 GitHub API + 本地 master tip):
正在做: 按 CI 协调政策把 |
…ed, per #4599 coordination)
(ai: vllm-qwen/qwen3.8-27b) Review verdict — PR #6001 (head Independently re-verified (not taken from the issue text): live PR metadata + full 5-file diff; pre-change rule text at master tip; the #6000 thread confirming owner chose option 2 (root Behavior change (disclosed): old spec "root keeps only Diff cleanliness: 5 files, one-line hunks, every line on-topic. One addition made during review: merged CI: first run red solely from the inherited master-level gate (test added by #5989 unregistered in LIVE_FILES; all 12 shards died pre-test; reproduced locally at master tip). Rerun on 结构化八问
判定:可合。 内容审核通过 + CI 全绿( |
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.1114-master.5c3c268 # this exact build
npm install -g billion-context@master # always the newest merged build
|
…ocale translations, ranxianglei#5956 reasoning-replay after cut, ranxianglei#5957 non-stream anthropic proxy loop, ranxianglei#5958 degenerate retry error shape
What
Carve out a bounded exception to the Documentation Layout rule ("repo root keeps only four entry files") so the root may also hold recognized community-maintained README translations (
README.<locale>.md).Why
Owner approved option 2 for #6000 (2026-11-09): the Japanese README lives at the root as
README.ja.md, using GitHub's nativeREADME.<locale>.mdconvention so the top-right language switcher picks it up automatically. Without this carve-out, adding a rootREADME.ja.mdwould contradict the written rule in five places.Scope
Docs-only — no code, wire, config, or persistence change. Amended consistently in all five locations that state the rule:
AGENTS.md§3 "Documentation Layout" (One hub)docs/index.md,docs/index.zh-CN.mddocs/README.md,docs/README.zh-CN.mdThe four core entry files stay locked; new non-translation docs still go in
docs/.Split with the translation PR
This PR is the enabling rule change (maintainer-owned spec edit). The actual
README.ja.mdplus the 「日本語」 language-link entries inREADME.md/README.zh-CN.mdcome from @eltociear's separate translation PR, which will close #6000. Disjoint files; sequenced rule-first → translation-second.Refs #6000