feat(cloud-agent-next): add exact message result polling

[eshurakov]

Summary

• Add a bearer-protected getMessageResult tRPC query so asynchronous CLI clients can poll one submitted Cloud Agent turn by exact messageId.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Executive Summary

The getMessageResult tRPC query is well-implemented with thorough ownership isolation, strict output schema allowlisting, and comprehensive test coverage at both unit and integration levels.

Files Reviewed (11 files)

• services/cloud-agent-next/README.md
• services/cloud-agent-next/src/persistence/CloudAgentSession.ts
• services/cloud-agent-next/src/router.test.ts
• services/cloud-agent-next/src/router/handlers/session-management.ts
• services/cloud-agent-next/src/router/schemas.test.ts
• services/cloud-agent-next/src/router/schemas.ts
• services/cloud-agent-next/src/session/message-result.test.ts
• services/cloud-agent-next/src/session/message-result.ts
• services/cloud-agent-next/src/session/queries/events.ts
• services/cloud-agent-next/src/session/session-message-state.ts
• services/cloud-agent-next/test/integration/session/message-result.test.ts

---

Notable design decisions verified:

• getAssistantMessageById SQL uses LIMIT 1 without ORDER BY — safe because entity_id is declared UNIQUE in the events table schema, guaranteeing at most one matching row.
• requireSessionId() is called after storage reads in getMessageResult, but cannot throw: metadata presence at line 988 guarantees identity.sessionId exists (required field in CurrentSessionMetadataSchema).
• running status (mapped from internal accepted) correctly allows acceptedAt but blocks terminalAt, completionSource, failure, gateResult, and assistant through the superRefine constraints.
• The AssertTrue compile-time guard in session-message-state.ts ensures the public SessionMessageFailureStage/SessionMessageFailureCode enums stay in sync with CloudAgentRunStateReport at the type level.
• Pending-only compatibility fallback uses a full prefix scan (storage.list()), which is an existing pre-PR pattern, not a new performance concern.

Fix these issues in Kilo Cloud

---

_{Reviewed by claude-4.6-sonnet-20260217 · 3,830,315 tokens}

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