Repository navigation
fix: MARKER_INTEGRITY_NOTE silence clause — stop model narration around ACP calls - #899
Conversation
📦 Built Package ArtifactBranch: Option A — Install from npm PR tag (recommended)npm install -g billion-context@pr-899Each push to this PR publishes a new version under the Option B — Download artifact
tar xzf billion-context-pr899.tgz
npm install -g packageInstall instructions are refreshed on each push. |
[bot] 🏷 Verified this PR end-to-end (agent-authored per What I checked
Auto-merge gate (§7.4) — passes all eight items: single-module scoped, pure Merging stays human-only per repo rules — please merge when ready: #899 中文摘要:为 |
853d83e to
a195bc1
Compare
…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.
a195bc1 to
cb077bd
Compare
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 unconditionalwithMarkerIntegrityNotepath — no new config surface. The #717 comment above the constant is extended with the observation source.tests/marker-echo.test.tspins 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.