feat: show a delivered session message's body, with its header and guidance folded

[spacedragon]

Why

When one session sends another a message (an agent call, a reply, a task's input, or a task's round report), the console showed the model's whole input as the message. A task report in webchat read like this:

[Message msg-…] Report from your task (session …):
[task finished] Task webchat:a2a:…:subsession:… finished this round of work. Its final output, delivered on its behalf:

<the actual result>

To give it more work in the same context, call sendMessage with {"action":"messageTask","taskId":"…","message":"..."}.

Speak to the people here in the language they use, even when this report is in another.

The header and the guidance are for the model, not for the person reading.

What changed

Daemon (collab/session-message.ts, collab/coordinator.ts, daemon.ts, assistant/{tasks,patrol}.ts)

• Every session-message builder now produces three things instead of one string:
  • text: the readable part. For a call, reply or task input that is its body; for a task report, the task's final output or its one-line status.
  • turnBody.prompt: the rendered message, unchanged. The model reads it first everywhere: first delivery (session-manager), replay and context refresh (transcriptPromptText), and steering. Inbox replay carries turnBody too.
  • turnBody.sessionMessage: the header facts plus the guidance verbatim as notes.
• renderInput becomes sessionInput.
• Task round reports carry a shown part beside their text: the output, or the status line, plus the framing and the messageTask call. On a later session of the place, the hint swap applies to the folded note as well. Rows written before this change fall back to showing the whole text.
• A wake paired with a visible platform post (transcriptTs) is left exactly as it was. It lands on that post's row, whose text and replay stay the post's own.

Protocol

• New SessionMessageTurnFacts on UserTurnBody.sessionMessage: id, kind, source agent, label and session, inReplyTo, replyRequested, startsTask, and notes.

Web

• parseUserTurnBody validates the new fact, failing closed like the others.
• The transcript step carries it. The bubble gets a one-line caption, such as "Reply from reviewer" or "Report from a background task". Under "more", the UserTurnDetails fold shows the sender, session, message id, the message it answers, whether it awaits a reply, and "Guidance the agent received". The prompt itself is still never shown.
• This applies both to agent bubbles and to the user-side bubble used for an agent the page doesn't list. Webchat renders through the same view.
• en and zh-CN strings are added.

Side effects, all toward the body: session titles no longer start with [Message msg-…]. Recall excerpts, memory dream input, and the context post a webchat peer receives now carry the body instead of another session's header and reply instructions.

Docs: send-message-guide.md §9.5 records the split.

Verification

• Typecheck is clean for protocol, daemon, web and control plane. Eslint and prettier are clean.
• The full web suite passes locally (365 files, 3806 tests). Protocol tests pass (752).
• These daemon suites pass: sendMessage, collab, assistant, webchat and session-manager (24 files).
• Existing assertions about what the model receives now read turnBody.prompt ?? text, through a modelText helper. They still pin the exact rendered prompt.
• New tests:
  • session-message-display.test.ts: the split, notes, and a report with and without output.
  • daemon-message-agent: the call's display and facts, and the paired-post exemption.
  • subsession-continuation: task input facts, and a report's shown status with its folded notes.
  • Web: the parser, the fold, and a SessionDetailView page test where the caption and body show, the prompt never does, and the fold reveals the facts and guidance.

🤖 Generated with Claude Code · Claude Opus 5.5

[agentconnect-md-test]

Reviewed revision fbb1531. No blocking findings.

The display split preserves the rendered model prompt through initial delivery, inbox persistence, replay, and context refresh. Paired visible posts retain their existing behavior, and the console handles both agent and user-side message bubbles.

Validation: diff check passed. I could not run tests locally because this checkout has no installed dependencies or pnpm; CI is still pending.

_{sent by review-bot (Codex · gpt-6-astra) · open in session}