feat(runtime): report a provider dropping context across the send boundary

The provider-dropping note compared each step's input against the previous
step's, so it only saw a provider evicting context from inside one send. The
shape it exists for is not visible there: a provider that truncates to a fixed
window reports the same input on every later request while the user keeps
adding turns, and a send of one or two steps has no earlier step to compare
with. The live evidence in #4623 plateaus at 3,716 input tokens across eight
turns with nothing reported, which is the case the note was written for.

The first request of a send now compares against the last request a provider
accepted before it, read from the persisted anchor, which is route-validated
where it is read. A fold before that request would explain a smaller input by
itself, so it disables the comparison, as prunes, image omissions and a
shrinking tool set already do.

The note is now reported once per session rather than once per send. The
condition persists once a provider starts truncating, so a note on every later
turn would repeat one fact the user has already been told.

Refs #4559, #4623

Generated-by: Claude Code
Claude-Session: https://claude.ai/code/session_014ajaRxC4jydavY9nYUFj5J

Author: Joob1n

CHANGELOG.md

@@ -49,6 +49,7 @@
   and SessionEvent-to-RuntimeEvent conversion remains a pure mapper.
 - Retired the Task Ledger domain: SessionTodo is now the sole authority for in-session work items, and the operational-state schema drops the `workflow_task_ledger_events` table on first open. **Unfinished Tasks are not migrated and are permanently deleted.** This affects workspaces last opened by `v0.1.0` through `v0.1.11`, `cli-v0.1.0-beta.1`, `v0.2.0-incubating-rc1`, or a `v0.2.0-dev` build; those releases wrote Tasks to a table that no shipped build ever bridged into SessionTodo. Before opening such a workspace with this build, finish or export the Tasks you still need, or copy the workspace's `runtime.sqlite` aside — the migration removes the only live copy, so afterwards recovery requires a backup made in advance.
 - `token_usage` anchors now record the model and connection that produced them. A token count is a number in one model's tokenizer against one connection; carrying the route on the record lets any reader apply the rule the runtime already enforces, instead of pairing one model's usage with another model's window. The record decodes against a closed allowlist, so sessions written with these keys do not open in earlier releases, and the Runtime Host compatibility epoch moves to 107.
+- The provider-dropping note now also fires across the send boundary. A provider that truncates to a fixed window reports the same input on every later request while the user keeps adding turns, which a send of one or two steps cannot see from the inside; the first request of a send compares against the persisted anchor instead. Across the boundary the test is equality rather than "did not grow": inside a send Maka knows it only appended, while across it a manual compaction, a smaller tool set or an edited history all shrink the input legitimately, and none of them lands on exactly the same count. The note carries the two counts it compared, and is reported once per backend rather than once per send, because the condition persists once it starts.
 - Let the provider decide whether a request fits. Proactive compaction now uses only a user-declared Maka window and the previous accepted request's provider-reported `inputTokens + outputTokens`; no declaration means no proactive capacity threshold. `/models` and generated model metadata are display hints, not limits. `token_usage` records persist the last-request anchor under `lastRequestAnchor`; its new `{ inputTokens, outputTokens }` shape still decodes the retired `payloadChars` key from older sessions. Requests that are too large are compacted and retried once after a real provider rejection, then reported as a `context_overflow` provider error. Compaction is entered at most once per send, and a request rejected after a fold was actually applied is reported as still too large after compaction. A fold that failed open makes no such claim: that request went out with its full raw history. A reply cut at `finishReason: length` no longer triggers a fold, because the provider running out of window room and the provider's own lower output cap are indistinguishable from outside. Five system notes explain the provider-side cases: dropping context, a window worth declaring, an exchange past the declared window, a request accepted past the window the model reports (once per crossing, while nothing is declared), and a request still too large after compaction. The reply reserve that arms the proactive threshold is twice the last real reply, bounded at 8,000 tokens, rather than the model's maximum output. **Sessions this build writes do not open in earlier releases:** those decode `token_usage` against a closed allowlist, so the reshaped `lastRequestAnchor` key fails the record and, with it, the Session that contains it; downgrading therefore needs a copy of the workspace's `runtime.sqlite` taken before the upgrade. Nothing produces the `context_budget_exhausted` stop reason any more — a request that really is too large is compacted and retried once, then reported as a `context_overflow` provider error — though sessions that already recorded it still decode and present. The Runtime Host compatibility epoch moves to 106.
 - Unified context management under one Runtime-owned policy. `MAKA_CONTEXT_*` environment overrides no longer tune or disable compaction and Tool Result pruning; model-visible archive placeholders are read on demand through bounded `ArchiveRead` calls instead of eager hydration. Previously supported overrides are ignored on upgrade: if Tool Result pruning was set to `off`, pruning is re-enabled, and there is currently no supported replacement opt-out.
 - Moved Read image snapshots into the durable context-offload store with Runtime-owned

packages/cli/src/pi-transcript.ts

@@ -1345,8 +1345,17 @@ function systemNoteText(message: SystemNoteMessage): string | undefined {
       return 'Context compacted to keep this task within the model window.';
     case 'context_compaction_failed_open':
       return 'Context summary failed; the session continued without a new summary.';
-    case 'context_provider_dropping':
-      return 'The provider is dropping or rewriting context: content was appended but its reported usage did not grow. Declare a context window for this model so Maka compacts first.';
+    case 'context_provider_dropping': {
+      const data = message.data as
+        | { inputTokens?: unknown; priorInputTokens?: unknown }
+        | undefined;
+      const used = typeof data?.inputTokens === 'number' ? data.inputTokens : undefined;
+      const prior = typeof data?.priorInputTokens === 'number' ? data.priorInputTokens : undefined;
+      if (used === undefined || prior === undefined) {
+        return 'The provider is dropping or rewriting context: content was appended but its reported usage did not grow. Declare a context window for this model so Maka compacts first.';
+      }
+      return `The provider is dropping or rewriting context: content was appended, and it counted ${used} input tokens against ${prior} before, which is no growth. Declare a context window for this model so Maka compacts first.`;
+    }
     case 'context_overflow_after_compaction':
       return 'History was compacted and the provider still called this request too large. What remains also carries the system prompt, the tool schemas, the summary and the recent tail; shortening this message is the part you control.';
     case 'context_reported_window_exceeded': {

packages/runtime/src/__tests__/mid-turn-capacity-backend.test.ts

@@ -147,6 +147,8 @@ interface MidTurnFixtureOptions {
   firstResult?: string;
   /** The model finishes on the second request instead of running three steps. */
   finalAtSecondCall?: boolean;
+  /** One request and no tool call, so only the step-0 comparison can fire. */
+  singleRequest?: boolean;
   /** Add a third tool step whose result outgrows even a rolled-forward fold (finding A). */
   rollingOverflow?: boolean;
   /** Tool-search availability with a huge deferred schema (finding D). */
@@ -263,6 +265,7 @@ function buildFixture(options: MidTurnFixtureOptions = {}): MidTurnFixture {
     if (options.bigToolGroup) {
       return call === 1 ? toolCallChunks('tool-1', 'tool_search', { query: 'Big' }) : doneChunks();
     }
+    if (options.singleRequest) return doneChunks();
     if (call === 1) {
       const first = toolCallChunks('tool-1', 'Read', { path: 'one.md' });
       if (!options.assistantTextInFirstStep) return first;
@@ -1292,6 +1295,87 @@ function defineMidTurnSuite(consumer: ConsumerMode): void {
     );
   });
 
+  test('reports provider context dropping across the send boundary', async () => {
+    // The Ollama shape: the provider truncates to its own window, so the input
+    // it counts is the SAME on every later request while the user keeps adding
+    // turns. A send of one or two steps never sees that from the inside
+    // (#4623). One request here, so only the step-0 comparison can write it.
+    const fixture = buildFixture({
+      withoutContextWindow: true,
+      singleRequest: true,
+      finalStepUsage: { input: 3_716, output: 10 },
+      extraPriorEvents: [priorUsageEvent({ inputTokens: 3_716, outputTokens: 12 })],
+      priorRunHeaders: [priorRunHeader()],
+    });
+    await runFixtureTurn(fixture, consumer);
+
+    const note = fixture.messages.find(
+      (message): message is { type: 'system_note'; kind: string; data?: unknown } =>
+        (message as { kind?: string }).kind === 'context_provider_dropping',
+    );
+    assert.deepEqual(note?.data, { inputTokens: 3_716, priorInputTokens: 3_716 });
+  });
+
+  test('does not report dropping across the boundary when the input grew', async () => {
+    const fixture = buildFixture({
+      withoutContextWindow: true,
+      singleRequest: true,
+      finalStepUsage: { input: 4_000, output: 10 },
+      extraPriorEvents: [priorUsageEvent({ inputTokens: 3_716, outputTokens: 12 })],
+      priorRunHeaders: [priorRunHeader()],
+    });
+    await runFixtureTurn(fixture, consumer);
+
+    assert.equal(
+      fixture.messages.some(
+        (message) => (message as { kind?: string }).kind === 'context_provider_dropping',
+      ),
+      false,
+    );
+  });
+
+  test('does not report dropping across the boundary when the input merely shrank', async () => {
+    // A manual compaction leaves the pre-compaction anchor behind, a turn can
+    // carry a smaller tool set, and a user can edit or branch history. All
+    // three shrink the input legitimately, and none lands on exactly the same
+    // count, so equality is what separates them from a truncating provider.
+    const fixture = buildFixture({
+      withoutContextWindow: true,
+      singleRequest: true,
+      finalStepUsage: { input: 900, output: 10 },
+      extraPriorEvents: [priorUsageEvent({ inputTokens: 3_716, outputTokens: 12 })],
+      priorRunHeaders: [priorRunHeader()],
+    });
+    await runFixtureTurn(fixture, consumer);
+
+    assert.equal(
+      fixture.messages.some(
+        (message) => (message as { kind?: string }).kind === 'context_provider_dropping',
+      ),
+      false,
+    );
+  });
+
+  test('does not report dropping across the boundary when this send folded first', async () => {
+    // A fold before the first request explains a smaller input by itself.
+    const fixture = buildFixture({
+      contextWindow: 3_000,
+      singleRequest: true,
+      finalStepUsage: { input: 3_716, output: 10 },
+      extraPriorEvents: [priorUsageEvent({ inputTokens: 3_716, outputTokens: 12 })],
+      priorRunHeaders: [priorRunHeader()],
+    });
+    await runFixtureTurn(fixture, consumer);
+
+    assert.equal(fixture.summarizerCalls, 1);
+    assert.equal(
+      fixture.messages.some(
+        (message) => (message as { kind?: string }).kind === 'context_provider_dropping',
+      ),
+      false,
+    );
+  });
+
   test('records provider context dropping when an append-only step reports the same usage', async () => {
     // The Ollama shape: the provider truncates to its own window, so input
     // stops growing rather than dropping while Maka keeps appending. A

packages/runtime/src/ai-sdk-backend.ts

@@ -1072,6 +1072,15 @@ export class AiSdkBackend implements AgentBackend {
    */
   private readonly activeTurns = new Set<TurnScope>();
   private readonly compaction: AiSdkCompaction;
+  /**
+   * The provider has been reported dropping context, for this backend.
+   *
+   * Not per send: the condition persists once a provider starts truncating, so
+   * a note on every later turn would repeat one fact the user has already been
+   * told. The scope is this backend's lifetime rather than the Session's, so a
+   * backend that is disposed and rebuilt may say it once more.
+   */
+  private contextProviderDroppingReported = false;
   /** Session-scoped running total, deliberately accumulated across turns. */
   private cumulativeUsageCheckpoint: NormalizedAiSdkUsage | undefined;
   private readonly memoryReplayMessageEvents = new WeakMap<ModelMessage, readonly string[]>();
@@ -1565,7 +1574,6 @@ export class AiSdkBackend implements AgentBackend {
     let contextBudgetForTelemetry: ContextBudgetDiagnostic | undefined;
     let contextCompactedNoteWritten = false;
     let contextCompactionFailedOpenNoteWritten = false;
-    let contextProviderDroppingNoteWritten = false;
     let contextWindowOverrunNoteWritten = false;
     let contextReportedWindowNoteWritten = false;
     let contextOverflowAfterCompactionNoteWritten = false;
@@ -2188,27 +2196,55 @@ export class AiSdkBackend implements AgentBackend {
                   const toolSchemaShrank =
                     lastStepActiveToolCount !== undefined &&
                     activeToolsForRequest.length < lastStepActiveToolCount;
+                  // Across the send boundary the comparison is the same one,
+                  // against the last request a provider accepted before this
+                  // send. A provider that truncates to a fixed window reports
+                  // the same input on every later request while the user keeps
+                  // adding turns, and a send of one or two steps never sees
+                  // that from the inside: the live evidence plateaus at 3,716
+                  // input tokens across eight turns with nothing reported
+                  // (#4623). The first request of a send therefore compares
+                  // against the persisted anchor, which is route-validated
+                  // where it is read; a fold before that request would explain
+                  // a smaller input by itself, so it disables the comparison.
+                  const acrossSends = completedRequestIndex === 0;
+                  const priorInput = acrossSends
+                    ? midTurnState?.compactionAppliedThisSend === true
+                      ? undefined
+                      : midTurnState?.priorAcceptedInputTokens
+                    : lastStepInputTokens;
                   if (
-                    !contextProviderDroppingNoteWritten &&
+                    !this.contextProviderDroppingReported &&
                     !toolSchemaShrank &&
                     midTurnState &&
-                    completedRequestIndex >= 1 &&
-                    lastStepInputTokens !== undefined &&
+                    priorInput !== undefined &&
                     midTurnState.replacedStepNumber !== completedRequestIndex &&
                     pruneAppliedAtStep !== completedRequestIndex &&
                     midTurnState.omittedImageToolResults.size === 0 &&
                     stepUsage !== undefined &&
                     Number.isFinite(stepUsage.inputTokens) &&
                     stepUsage.inputTokens > 0 &&
-                    stepUsage.inputTokens <= lastStepInputTokens
+                    // Across sends the test is equality, not "did not grow".
+                    // Inside a send Maka knows it only appended, so any
+                    // shortfall is the provider's. Across the boundary it does
+                    // not: a manual compaction leaves the pre-compaction anchor
+                    // behind, a turn can carry a smaller tool set, and a user
+                    // can edit or branch history. All three shrink the input
+                    // legitimately, and none of them lands on exactly the same
+                    // count. A provider truncating to a fixed window does, on
+                    // every later request.
+                    (acrossSends
+                      ? stepUsage.inputTokens === priorInput
+                      : stepUsage.inputTokens <= priorInput)
                   ) {
-                    contextProviderDroppingNoteWritten = true;
+                    this.contextProviderDroppingReported = true;
                     const note: SystemNoteMessage = {
                       type: 'system_note',
                       id: this.newId(),
                       turnId,
                       ts: this.now(),
                       kind: 'context_provider_dropping',
+                      data: { inputTokens: stepUsage.inputTokens, priorInputTokens: priorInput },
                     };
                     await this.input.appendMessage(note).catch(() => {});
                   }

packages/runtime/src/ai-sdk-compaction.ts

@@ -814,6 +814,7 @@ export class AiSdkCompaction {
     if (persisted) {
       state.baselineTokens = persisted.inputTokens + (persisted.outputTokens ?? 0);
       state.lastAcceptedTotalTokens = state.baselineTokens;
+      state.priorAcceptedInputTokens = persisted.inputTokens;
     }
     if (persisted) state.replyReserveTokens = replyReserveTokens(persisted.outputTokens);
     return state;
@@ -1459,6 +1460,14 @@ export class MidTurnCapacityCompactState {
    * rejection about what remains in it.
    */
   compactionAppliedThisSend = false;
+  /**
+   * Input tokens of the last request a provider accepted before this send.
+   *
+   * Input against input, across the send boundary: the first request of a send
+   * has no earlier step to compare with, and `baselineTokens` counts the reply
+   * too, which the next request does not always carry.
+   */
+  priorAcceptedInputTokens: number | undefined;
 
   constructor(
     readonly headAnchor: RuntimeEvent,

packages/ui/src/conversation-copy.ts

@@ -320,7 +320,7 @@ export interface ConversationCopy {
     systemNotes: {
       contextCompacted: string;
       contextCompactionFailedOpen: string;
-      contextProviderDropping: string;
+      contextProviderDropping: (used: number, prior: number) => string;
       contextWindowSuggestion: (tokens: number, declared: number | undefined) => string;
       contextWindowOverrun: (used: number, declared: number) => string;
       contextReportedWindowExceeded: (used: number, reported: number) => string;
@@ -541,7 +541,8 @@ const CONVERSATION_COPY = {
       systemNotes: {
         contextCompacted: '已压缩较早的对话内容，以适应模型上下文窗口。',
         contextCompactionFailedOpen: '上下文摘要失败；本轮已在未生成新摘要的情况下继续。',
-        contextProviderDropping: '供应商在丢弃或改写上下文（追加了内容但用量未增长）。在连接设置里为该模型声明上下文窗口，让 Maka 先行压缩。',
+        contextProviderDropping: (used, prior) =>
+          `供应商在丢弃或改写上下文：追加了内容，它报告的输入却是 ${used.toLocaleString('zh-CN')} tokens，与之前的 ${prior.toLocaleString('zh-CN')} 相比没有增长。在连接设置里为该模型声明上下文窗口，让 Maka 先行压缩。`,
         contextWindowSuggestion: (tokens, declared) =>
           declared === undefined
             ? `供应商拒绝了这次请求。该模型未声明上下文窗口；上次成功的用量约 ${tokens} tokens，可将窗口设为该值让 Maka 先行压缩。`
@@ -714,7 +715,8 @@ const CONVERSATION_COPY = {
       systemNotes: {
         contextCompacted: 'Context compacted to keep this session within the model window.',
         contextCompactionFailedOpen: 'Context summary failed; the session continued without a new summary.',
-        contextProviderDropping: 'The provider is dropping or rewriting context (content was appended but usage did not grow). Declare a context window for this model in the connection settings so Maka compacts first.',
+        contextProviderDropping: (used, prior) =>
+          `The provider is dropping or rewriting context: content was appended, and it counted ${used.toLocaleString('en-US')} input tokens against ${prior.toLocaleString('en-US')} before, which is no growth. Declare a context window for this model in the connection settings so Maka compacts first.`,
         contextWindowSuggestion: (tokens, declared) =>
           declared === undefined
             ? `The provider rejected this request. No context window is declared for this model; the last accepted usage was about ${tokens} tokens — set the window to that value so Maka compacts first.`