fix(cloud-agent-sdk): stop dropping entity-upsert stream events

[eshurakov]

Summary

Live cloud-agent tool cards were stuck on spinners (bash...) until page reload. Root cause: PR #4987 added client-side filtering that dropped stream frames with eventId <= lastEventId.

The Durable Object entity-upserts tool/message parts under a stable SQLite row id and rebroadcasts that same (or older) eventId with a newer payload (pending → running → completed). Filtering by id dropped those live updates; REST history on reload still had the final state, so reload looked fine.

This removes the client-side eventId drop entirely. lastEventId remains only as a high-water mark for reconnect fromId. Exclusive DO fromId (id > fromId) already handles replay catch-up.

Test plan

• pnpm test -- cloud-agent-transport.test.ts in packages/cloud-agent-sdk (42 passed)
• Live cloud agent session: run parallel bash tools and confirm cards leave the spinner and show command/output without reload
• Reconnect mid-session and confirm stream still advances via fromId

[kilo-code-bot]

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	0
SUGGESTION	1

The core fix is sound: removing client-side eventId filtering restores live entity-upsert rebroadcasts (tool cards leaving the spinner), and lastEventId is correctly kept as a monotonic high-water mark for reconnect fromId. I verified that every positive-id event type affected by the new at-least-once delivery (message.updated, message.part.updated, message.part.removed, session.*, complete/interrupted/error, autocommit_*) maps to idempotent sink handlers (upsert/delete/state transitions), and that non-idempotent message.part.delta events are broadcast-only with eventId: 0, so they were never subject to the removed filter. Tests were updated consistently with the new semantics.

Issue Details (click to expand)

SUGGESTION

File	Line	Issue
packages/cloud-agent-sdk/src/cloud-agent-transport.test.ts	1296	Stale section banner // Exactly-once event replay contradicts the renamed describe block and the new at-least-once assertions

Files Reviewed (2 files)

• packages/cloud-agent-sdk/src/cloud-agent-transport.ts - 0 issues
• packages/cloud-agent-sdk/src/cloud-agent-transport.test.ts - 1 issue

Fix these issues in Kilo Cloud

---

_{Reviewed by kimi-k3 · Input: 80.1K · Output: 20.3K · Cached: 1.5M}

_{Review guidance: REVIEW.md from base branch main}