desktop: sent user message not visible in chat — client sends limit=0 on message fetch, server rejects with 400

Summary

OpenCode Desktop beta (Windows): after sending a message, the user's own message text does not appear in the chat transcript, even though the message is received and stored server-side. Server logs show the desktop client calling GET /api/session/<id>/message with limit=0, which the API rejects with HTTP 400, so the message list never refreshes.

Environment

• opencode version: 0.0.0-next-17400/17403 server, desktop app v0.0.0-beta-17402
• OS: Windows 10.0.26200 (win32 x64)
• Terminal: OpenCode Desktop app (Electron beta build)
• Shell: C:\WINDOWS\system32\cmd.exe
• Install/channel: beta / next
• Active plugins: claude-mem.js (local), opencode-see-image@1.3.0

Reproduction

1. Open the desktop beta app and start or continue a session.
2. Type a message and send it.
3. The assistant responds (message is received), but the typed user message never renders in the chat transcript.

Occurs intermittently; also observed while the server was healthy (this is not the "Path is not absolute" 500 regression).

Expected Behavior

Sent user messages appear immediately in the chat transcript.

Actual Behavior

The message is stored server-side (verified via opencode2 api get /api/session/<id>/message — the message exists) but is not shown in the UI. Server log (role=server) shows the client sending an invalid request:

level=WARN message="schema rejection" kind=Query
  reason="Expected a value greater than or equal to 1, got 0\n  at [\"limit\"]"
level=INFO message="Sent HTTP response" http.method=GET
  http.url=/api/session/ses_.../message http.status=400

The desktop client is sending limit=0 on the message-list request, which the schema rejects (limit must be >= 1), so the chat list never refreshes with the new message.

Additional Context

• Recurs intermittently; service restart does not fix it.
• Possibly related to existing desktop issues #31200 / #31292 / #28228 (composer draft loss), but this is a different symptom: sent messages missing from the transcript.
• Also see #42266 for a related desktop sidecar regression (all API 500s) observed on the same setup.