Skip to content

fix: MARKER_INTEGRITY_NOTE silence clause — stop model narration around ACP calls - #899

Merged
ranxianglei merged 1 commit into
masterfrom
2026-09-17_marker-integrity-silence
Sep 20, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-09-17_marker-integrity-silence

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Follow-up to #862 (marker-suppression item 2 of 2 confirmed by the reporter).

Problem

In the #862 deployment (ZCode/ACP) the model was observed narrating around genuine proxy executions: it emitted its own marker-style confirmation lines plus preambles and completion summaries (including non-English commentary) before and after each real compression. Distinct from #717 (which faked compressions that never happened) — here the tool call really ran, but the model still added its own marker/summary text around it.

Change

Appends one sentence to MARKER_INTEGRITY_NOTE (src/compress-tool.ts): execute these calls silently — no announcement/preamble before the call, no completion summary, status line, or marker-style line after it; continue the task directly as if the call had not happened. The constant stays byte-stable (prefix-cache safe) and reaches every nudge + injected philosophy prompt via the existing unconditional withMarkerIntegrityNote path — no new config surface. The #717 comment above the constant is extended with the observation source. tests/marker-echo.test.ts pins the new clause.

The #717 anti-forgery stripping of model-emitted markers is untouched and remains active in both modes; pairs with #893 (compress.visibilityMarkers) which removes the imitation target itself.

Pre-flight on master @ 55da3f0 (v0.1.117): typecheck clean · npm test 1668 pass / 0 fail / 2 skipped · tsup build ok.

@github-actions

github-actions Bot commented Sep 17, 2026 •

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-09-17_marker-integrity-silence (cb077bd)

Option A — Install from npm PR tag (recommended)

npm install -g billion-context@pr-899

Each push to this PR publishes a new version under the pr-899 npm tag.

Option B — Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr899.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 Verified this PR end-to-end (agent-authored per ework-agent-pr marker — reviewed, did not redo). Ready to merge.

What I checked

  1. Base & shape — single commit 853d83e on top of current master 55da3f0 (v0.1.117); no stale base, no rebase needed. Diff is exactly 2 files, +6/−2: the MARKER_INTEGRITY_NOTE constant (+ its 模型把 "📦 [ACP] Compressed" 确认标记伪造为普通 assistant 文本——17 次假压缩、0 次真实执行(自我回执幻觉) #717 comment extended with the [Question] zocde调用子智能体的时候,子智能体有概率出错,导致子智能体停止工作 #862 observation source) and one assertion in tests/marker-echo.test.ts. No unrelated churn.

  2. Wiring claim holds — withMarkerIntegrityNote is unconditional (text + MARKER_INTEGRITY_NOTE, no config gate) and is applied at every nudge injection point (src/server.ts:1904, :2045, :2250) and every injected compress-system-prompt path (src/server.ts:2024, :2220, :2558, :3736) — so the clause reaches both plugin mode and proxy mode with no new config surface.

  3. Prefix-cache safety — the new sentence is appended to the tail of the constant; every existing byte of the note is unchanged, so cached prefixes remain valid.

  4. 模型把 "📦 [ACP] Compressed" 确认标记伪造为普通 assistant 文本——17 次假压缩、0 次真实执行(自我回执幻觉) #717 anti-forgery untouched — no other code changed; the forged-marker stripping tests sit directly beside the modified assertion and pass.

  5. CI — all four runs green on head 853d83e: CI, e2e-fake-codex, Windows codex overlay (E2E verify on real Windows: codex accepts CODEX_HOME overlay and registers the bili MCP server (#681 / PR #683) #686), PR Build Artifact.

  6. Local pre-flight on the PR head (independent re-run): typecheck clean · npm test 1668 pass / 0 fail / 2 skipped (matches your claimed numbers exactly) · tsup build ok · confirmed both the new silence clause and the original anti-forgery clause are present in dist/index.js.

Auto-merge gate (§7.4) — passes all eight items: single-module scoped, pure fix:, green on current master, no config-schema/persistence/wire/cross-repo changes, clean diff, references #862, touches none of the load-bearing infra (update.ts, kernel pin, ref/id logic, security). One honest caveat on gate item 2: model narration around real tool calls can't be unit-reproduced, so the text-pin assertion is the strongest regression guard available for a prompt-string change — acceptable here.

Merging stays human-only per repo rules — please merge when ready: #899

中文摘要:为 MARKER_INTEGRITY_NOTE 追加了静默执行条款(修 #862 部署中模型在真实压缩前后自我叙述/自造标记行的问题),改动仅一处常量尾部追加+一条测试断言,前缀缓存安全、双模式均生效、#717 防伪剥离不受影响;本地独立复跑 typecheck/1668 项测试/构建全绿,CI 四项全绿,可以合并。

…ool calls (#862)

#862 deployment observed the model narrating around genuine proxy executions: its own marker-style confirmation lines plus preambles and completion summaries (incl. non-English commentary) before/after each real compression. Appends a silence clause to the byte-stable integrity note (prefix-cache safe): no announcement before, no summary/status/marker-style line after; continue directly when the tool returns. Extends the #717 comment with the observation source; test pins the new clause.
@ranxianglei
ranxianglei force-pushed the 2026-09-17_marker-integrity-silence branch from a195bc1 to cb077bd Compare September 19, 2026 16:31
@ranxianglei
ranxianglei merged commit f3f1330 into master Sep 20, 2026
8 checks passed
@ranxianglei
ranxianglei deleted the 2026-09-17_marker-integrity-silence branch October 15, 2026 05:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant