Repository navigation
[PR] feat(acp-status): surface host-native compaction landings as an explicit per-session marker (#4458) - #4459
Closed
ranxianglei wants to merge 1 commit into
Closed
ranxianglei wants to merge 1 commit into
ranxianglei wants to merge 1 commit into
Conversation
…cit per-session marker (#4458) Add a HOST-NATIVE COMPACTION section to acp_status, shown per-session when a host-native compaction landing is recorded (session.metadata.nativeCompactionBoundary), in BOTH compression modes. It distinguishes "the host compacted this conversation" from "bili folded it", shows pending-rebase vs rebased state, and names the resolved client/lane. Proactive visibility ahead of the reactive DEAD REFS / breaker / conflict-watch surfaces, so an operator or agent can see a landing BEFORE a follow-up call burns a ref minted before the boundary. Additive display-only output: absent when no landing was recorded; no wire, config, cache, or identity impact. Regression test covers both gate directions (#3617).
ranxianglei
changed the title
Contributor
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g [email protected]This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr4459.tgz
npm install -g packageInstall instructions are refreshed on each push. |
Owner
Author
(ai: vllm-qwen/qwen3.8-27b) 查重: 不重复。本 PR 是 #4458 ask #2(在 标签: hermes, scope/ui, p1 —— hermes 是该缺陷家族的驱动案例(PR 本身 lane-neutral); 独立复核(非转述 issue 结论):
八问:
行为变更披露(有意,已在 PR 描述披露): 判定:可合。feat 类按 §7.4 需人工合并;CI 已全绿,定向测试本地复验通过,无阻塞项。ask #1(hermes 安装期禁用原生压缩)+ #3(hermes 补救提示行)留待后续 PR 跟进 #4458,本 PR 范围切割清晰,无异议。 |
ranxianglei
added
hermes
Owner
Author
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.
Adds ask #2 of #4458: an explicit, queryable per-session marker in
acp_statusfor host-native compaction landings.What
A new
HOST-NATIVE COMPACTIONsection appears inacp_statusoutput when a session has a recorded host-native compaction landing (session.metadata.nativeCompactionBoundary). It shows:conflictClientOf),at),NOT yet rebased(pending) vsrebased onto it at <ts>(done).It is lane-neutral and works in both compression modes: the boundary record is set server-side by every
prepare-*/relay path that detects a host-native rewrite (Google/Responses/Anthropic/OpenAI + relay), so hermes/codex/omp/etc. all surface it.Why
The existing surfaces are reactive —
DEAD REFS, the compress breaker receipt, and the conflict-watch section only speak after a failure or once dead refs materialize. This marker is proactive: an operator or agent can see "the host compacted this conversation under bili" before a follow-up call burns a ref minted before the boundary. That is the visibility gap #4458's reporter named ("surface host-native compaction landings as an explicit marker … BEFORE next call burns a dead ref").Scope — this PR ships only ask #2 of #4458
compression.enabledconfig-set path. They land as a follow-up PR referencing [Hermes lane] Disable Hermes' native auto-compaction during plugin setup, and surface host-native compaction landings as an explicit marker #4458. So this PR references but does not close [Hermes lane] Disable Hermes' native auto-compaction during plugin setup, and surface host-native compaction landings as an explicit marker #4458.Behavior change (disclosed)
Additive display-only output. For sessions with no native-compaction boundary the output is unchanged (section absent). Where one exists, one extra section is appended. No wire/protocol change, no new config/env, no cache or identity impact. Reasoned in both modes (boundary set server-side regardless of plugin/proxy mode).
Tests
New regression test asserts both gate directions (#3617): no boundary → no section; pending →
NOT yet rebased; rebased →rebased onto it at; lane name resolved frompluginAgent/clientHint. Targeted suites green locally (acp-status8/8,codex-official2/2); typecheck clean. Full-suite verdict = CI on the pushed head.References #4458.