Repository navigation
[PR] docs: message-identity hierarchy is now msgid > order > hash (#4491/#4834) - #4871
Merged
Merged
Conversation
…4834) The doctrine said stable client ids may only ever be join hints. That was written before the plugin lanes started shipping host msgids in a bili-private envelope (msgIds on the incremental turn / biliMsgIds stripped at ingress) and before #4834 made resolution id-first. Agents reading the docs concluded 'we have no msgids' — true on the model wire, false on the plugin lanes. - AGENTS.md KDD #11 retitled to the full hierarchy: msgid first where the envelope carries it (plugin lanes only, never forwarded upstream), order still primary on id-less resend reconciliation, hash stays the per-cell gate. Three-part PK (session_id, msg_id, content_hash) noted as safety belt. - AGENTS.md KDD #13 evolution updated to four stages (hash -> order -> msgid pinning -> snapshot render). - MESSAGE-IDENTITY.md: new section 'The msgid envelope' documenting the channel, all-or-nothing semantics, resync re-claim, #4834 id-first, #4863 claim-after-guard, and the boundary (model wire unchanged, tool-call ids are pairing keys, proxy-mode resends keep the ladder); Future-direction paragraph refreshed.
Contributor
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.861-master.13e0dba # this exact build
npm install -g billion-context@master # always the newest merged build
|
Contributor
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.6298-pr.4871.876a4adThis exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr4871.tgz
npm install -g packageInstall instructions are refreshed on each push. |
This was referenced Oct 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
这是啥问题
教义文档落后于代码:MESSAGE-IDENTITY.md 仍写着「未来若有稳定客户端消息 id,只能当 join hint,永不替代 content-hash 的账本 join 基础」。而 #4491 之后四条插件车道已经把宿主 msgid 作为 bili 私有信封字段上行并钉进账本,#4834 之后解析 id 优先(跨模型改写不再否决 id)。读文档的 agent 因此得出「我们没有 msgid」——模型线上对,插件车道上错。
改动
验证
纯文档改动;typecheck/build 确认未触碰代码。
关联
#4491(msgIds 信封) #4834(id-first) #4863(claim-after-guard) #2821(顺序中心 owner rule 原文)