From b362c675d6461012309c1471cc84085191e5a8a0 Mon Sep 17 00:00:00 2001
From: Lily Shen <115414357+lilyshen0722@users.noreply.github.com>
Date: Tue, 25 Aug 2026 01:55:28 -0700
Subject: [PATCH] docs(cli): mark the surviving `limit: 10` as a read, not a
 claim
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

@sprint-review (57766): after #1166 this is the only `limit: 10` left in
agent.js, and the reason it is fine is one function away and invisible here.
Anyone who greps the constant after reading that thread has to re-derive the
distinction — two identical strings, opposite significance, no local marker.

No behaviour change. The events fetch went to 1 because fetching an event
CLAIMS it; this endpoint returns pod messages for the echo check and claims
nothing, so ten rows cost ten rows.

Comment rather than a test because there is no wrong behaviour to pin — the
failure mode is a reader's question, and the answer belongs where the
question gets asked.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---
 cli/src/commands/agent.js | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/cli/src/commands/agent.js b/cli/src/commands/agent.js
index 9f7e10436..6df9440b8 100644
--- a/cli/src/commands/agent.js
+++ b/cli/src/commands/agent.js
@@ -803,6 +803,12 @@ export const performRun = ({
     // suppress a genuine reply (#757).
     const snapshotMessages = async () => {
       try {
+        // READ limit, not a claim. Since #1166 this is the only `limit: 10`
+        // left in the file, and the one it is easy to mistake it for — the
+        // events fetch — was reduced to 1 precisely because fetching an
+        // event CLAIMS it. This endpoint claims nothing: it returns pod
+        // messages so the echo check can see what is already there, and
+        // asking for ten costs ten rows.
         const { messages = [] } = await client.get(
           `/api/agents/runtime/pods/${eventPodId}/messages`, { limit: 10 },
         );