Repository navigation
docs: MESSAGE-IDENTITY — content hashes as the cross-turn join key (#1496) - #1506
Merged
Merged
Conversation
…1496) Design record settling #1496 at message granularity, sibling to SESSION-IDENTITY: the question is the join key (mNNNNN auto-increment already exists), content bytes are the only all-host all-lane stable key, failure-mode asymmetry (misattribution vs non-recognition), the #242 partial round-trip channel and why it is not identity, tags as derived views, and the lastPassIds echo-discrimination fix direction.
Contributor
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.1434-pr.1506.5c2b0b8This exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr1506.tgz
npm install -g packageInstall instructions are refreshed on each push. |
Owner
Author
交付物(与 issue 规格一致)
纯文档:4 files,+346/−0,零代码、零配置、零行为变更。单 commit,rebase 到当前 master(516f987)后推送。 Issue 七个要点全部落进文档,且逐条对过当前代码写之前把文档里每个代码级断言都在 master 上核了一遍(不是照抄 issue 描述):
一个写作细节:EN 文档里唯一一处字面渲染 tag 示例经字节级核查完整落盘(显示层会吞 acp 标记,磁盘内容无损)。 说明
中文摘要:按 issue 规格写完 MESSAGE-IDENTITY 双语文档并开 PR #1509(纯文档 +346 行,所有代码级论断已对当前 master 逐一核实),等待人工合并。 |
Merged
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.
What & why
Closes #1496 (documentation direction).
Adds
MESSAGE-IDENTITY.md+MESSAGE-IDENTITY.zh-CN.md, the message-granularity sibling ofSESSION-IDENTITY.md, settling the #1496 question: message identity stays content-derived; ingress-assigned ids do not replace the hash.Key points recorded:
input[].idis provider namespace ([Bug] Responses ACP round 2 生成 66 字符 message id,导致 Codex 后续请求持续 400 #242 64-char 400, fix: scope Responses ingress id healing to Bili's msg-proxy namespace #1475rsprefix, healing confined tomsg-proxy-*).remembered快照,长会话里 plugin 路径的compress全败(Requested range(s) cannot be anchored) #1307's 163/163); hash-join failure = non-recognition (self-healing perf loss).lastPassIdsecho discrimination — instance discrimination layered on top of the hash base, not a retreat to positional ids.Changes
MESSAGE-IDENTITY.md(new)MESSAGE-IDENTITY.zh-CN.md(new)README.md/README.zh-CN.md: one cross-reference line each, next to the existing SESSION-IDENTITY pointerBehavior changes
None — docs only.
Tests
None (docs only).
Config surface
None.