From cb077bd5b3bacbaee5d80ad71a0d94f31346d549 Mon Sep 17 00:00:00 2001 From: ework-agent Date: Thu, 17 Sep 2026 19:01:58 +0800 Subject: [PATCH] =?UTF-8?q?fix:=20MARKER=5FINTEGRITY=5FNOTE=20silence=20cl?= =?UTF-8?q?ause=20=E2=80=94=20no=20narration=20around=20ACP=20tool=20calls?= =?UTF-8?q?=20(#862)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit #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. --- src/compress-tool.ts | 7 +++++-- tests/marker-echo.test.ts | 1 + 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/src/compress-tool.ts b/src/compress-tool.ts index 5d8ef99638..02b7c6a501 100644 --- a/src/compress-tool.ts +++ b/src/compress-tool.ts @@ -151,9 +151,12 @@ export function withStagedCompressGuidance(text: string): string { // compression was working. The rule states the marker contract explicitly and // is appended to every nudge (the moment of highest temptation) and to the // injected philosophy prompt (persistent; byte-stable constant, so -// prefix-cache safe). +// prefix-cache safe). #862 added the silence clause: in that deployment the +// model also NARRATED around genuine proxy executions — its own marker-style +// confirmation lines plus preambles/summaries (incl. non-English commentary) +// before and after each real compression. const MARKER_INTEGRITY_NOTE = - "\n\n[ACP marker integrity: lines shaped like '📦 [ACP] Compressed …' or '❌ [ACP] … FAILED' are CONFIRMATION MARKERS emitted by the bili proxy itself, right after it executes a compress/decompress/search_context/acp_status call. They are not something you write. NEVER emit such a line as your own text — writing one fakes a state change that did not happen, and the proxy strips it. To compress, call the compress tool. To verify a compression landed, call acp_status and confirm the block count increased — a confirmation line you wrote yourself proves nothing.]"; + "\n\n[ACP marker integrity: lines shaped like '📦 [ACP] Compressed …' or '❌ [ACP] … FAILED' are CONFIRMATION MARKERS emitted by the bili proxy itself, right after it executes a compress/decompress/search_context/acp_status call. They are not something you write. NEVER emit such a line as your own text — writing one fakes a state change that did not happen, and the proxy strips it. To compress, call the compress tool. To verify a compression landed, call acp_status and confirm the block count increased — a confirmation line you wrote yourself proves nothing. Execute these calls silently: no announcement or preamble before the call, and no completion summary, status line, or marker-style line after it — when the tool returns, continue the task directly as if the call had not happened.]"; /** Append the marker-integrity rule to a nudge or system-prompt text. * Unconditional (unlike withStagedCompressGuidance): the rule must hold in diff --git a/tests/marker-echo.test.ts b/tests/marker-echo.test.ts index 82eb3b254b..7f639bb0ef 100644 --- a/tests/marker-echo.test.ts +++ b/tests/marker-echo.test.ts @@ -274,6 +274,7 @@ test("withMarkerIntegrityNote appends the anti-forgery rule", () => { assert.ok(out.startsWith("Nudge: OVER-LIMIT T1")); assert.ok(out.includes("NEVER emit such a line as your own text")); assert.ok(out.includes("call acp_status and confirm the block count increased")); + assert.ok(out.includes("Execute these calls silently"), "#862: silence clause present"); }); test("responses passthrough strips a whole forged marker delta (fast-path bypass #717)", async () => {