Skip to content

Commit 2cc224d

Browse files
test(server): a settled wait's restart-continuation check reads no messages again
The settled wait now checks restart continuations over the records it already loaded instead of re-reading the thread, so the query-count guard expects no extra message read. Co-Authored-By: Claude Opus 5.5 <[email protected]>
1 parent ceea9b8 commit 2cc224d

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

‎apps/server/src/mcp/OrchestratorMcpToolkit.integration.test.ts‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -658,10 +658,10 @@ describe("orchestrator MCP toolkit", () => {
658658
expect(
659659
messageReads.filter((query) => query.includes("$.notification.source.kind")),
660660
).toHaveLength(1);
661-
// The orchestrator's restart-continuation guard still reads its own records.
661+
// The restart-continuation guard reuses the records the wait already read.
662662
expect(
663663
messageReads.filter((query) => !query.includes("$.notification.source.kind")),
664-
).toHaveLength(1);
664+
).toHaveLength(0);
665665
const parentlessRead = yield* invoke(
666666
"t3_thread_read",
667667
{

0 commit comments

Comments
 (0)