feat: show agent conversations in the mobile inbox

[leynier]

Summary

A read-only Agent Conversations view in the mobile inbox, using the two read verbs on the phone allowlist.

• A Questions / Agent Conversations switch on the inbox screen.
• A conversation list with participant names (from inbox.targets when the terminal is a running agent, otherwise the handle), a Group badge, the message count, the workspace and age, and workspace filter chips.
• A detail screen with messages in order and a read-only notice. Only read verbs are ever sent.
• Data refreshes on conversationsChanged. An inbox reply push switches to Questions before it opens the thread.

Stacked on the desktop conversations PR.

Validation

• New agent_conversations_test (5 tests).
• flutter analyze reports no issues, and the full mobile flutter test passes (906 tests, 4 skipped).
• The max-lines ratchet and git diff --check pass.

Risk

The list loads at most 100 conversations. Not yet run against a paired phone.

[pullfrog]

Important

The inbox paste banner teaches agents a bash heredoc reply. That command fails in PowerShell 5.1, cmd, and nushell, so the reply path this feature pastes into the terminal does not work on Windows.

Reviewed changes

Reviewed the full stack against main: external inbox persistence and verbs, desktop and mobile inbox UI, and the read-only Agent Conversations view.

• Inbox store. ext: questions and replies live in the orchestration message table, with expiry, a pending cap, 7-day retention, and revision triggers. Delivered inbox questions are not expired.
• Host verbs. inbox.* is additive inboxV1 with no protocol bump. Phones may read and ask, not inbox.wait. Conversation reads do not mark agent messages read. inboxChanged and conversationsChanged are broadcast and listed for the desktop client.
• Desktop and mobile UI. A Questions / Agent Conversations switch, compose, follow-up, purge, and a read-only conversation detail. An inbox-reply push opens Questions, then the thread, and carries ids rather than reply text.
• CLI. alera inbox plus orchestration ask --no-wait and reply from --body, --body-file, or --body-stdin.

ℹ️ Nitpicks

• inbox_verbs_reach_the_hub_by_name never asserts inbox.conversations or inbox.conversation, so dropping those two from the hub reverse allowlist would still pass.

  ^{｜ Fix all ➔ ｜ Fix 👍s ➔ ｜ View workflow run ｜ Using grok-4.7 ｜ 𝕏}

[pullfrog]

ℹ️ No new issues in this delta.

Reviewed changes

Reviewed the mobile Agent Conversations commit since the prior review at 60b75dc1.

• Added read-only conversation reads. The phone calls inbox.conversations and inbox.conversation, parses the host's camelCase thread page and snake_case messages, and reloads only on conversationsChanged.
• Added the inbox switch. Questions / Agent Conversations hides Ask and Purge on the conversation list, which shows inbox.targets names, a Group badge, count, workspace, age, filter chips, and Load More.
• Routed ask and reply pushes to Questions. Opening a conversation sends only read verbs. An inbox-reply push and Ask Agent both select Questions before the thread opens.

  ^{｜ Fix it ➔ ｜ View workflow run ｜ Using grok-4.7 ｜ 𝕏}

[pullfrog]

✅ No new issues found.

Reviewed changes

Reviewed 029b8033 since the prior review at b5eba5a6. The conversations patch was rebased onto the desktop parent that extracted LoadMoreButton.

• Paged conversations through LoadMoreButton. A failed next page now shows the same snackbar as Questions instead of an unawaited error.

  ^{｜ View workflow run ｜ Using grok-4.7 ｜ 𝕏}