[pratikbuilds]

ConversationThread renders a reply conversation headed by its parent message, with a divider counting the replies, built from the same parts as the main conversation through a render prop. Each thread has its own Conversation, so a reply settles at the top of its own log, and in a keep-mounted panel tab a thread keeps its place and the host's draft while the reader switches tabs. The thread's PromptInput sits below the log, and aria-label or aria-labelledby names the log.

Stacked on #125: review only this commit. Part of #94.

Notes for review

• Props: parent, replies, renderMessage(message), sentId (this thread only), scrollPolicy (default settle), labels {log, replies(count)}; aria-label or aria-labelledby name the log; children (the thread's PromptInput) sit below the log. Stateless: no "use client".
• A thread that is unmounted, or given no size while hidden, loses its place: use PanelContent keepMounted.

Verification

• This commit passes bun run typecheck and bun run lint on its own (the stack is checked commit by commit).
• At the top of the stack: bun run check, bun run build, bun run dep-guard, bun run contrast-test and bun run test:e2e (Playwright specs and the Storybook axe sweep in light and dark) pass.

Closes #108

[corbits-triage]

Triage: In progress

Triage is waiting for CI to finish before it decides. This comment shows the verdict once it has.

[TheGreatAxios]

Automated multi-agent review: independent review + second-agent validation; only confirmed items listed. Clean composition PR — nothing blocking.

• minor src/ui/conversation-thread.tsx:44-49 (vs src/ui/conversation.tsx:601-621) — the sentId doc says a foreign id "moves nothing", which holds under settle but not stick: sent(id) glides to the end before any registry lookup, so any foreign-id change glides the thread to its end. Qualify the doc ("under settle…") or guard the stick branch on registry membership.
• file-for-later (plan follow-up) src/ui/conversation-thread.tsx:96-113 — no windowing slot: ConversationEarlier must sit first inside ConversationContent, but the thread owns the log's children and renders children outside the log as the input slot; the divider count is hardwired to replies.length. An optional earlier?: ReactNode slot plus seeding the count from parent.replies.count would close it.
• nits — labels.log is documented as the name "when no aria-labelledby is given" but an aria-label also overrides it (:18-20, 99-105); data-thread-parent/data-thread-divider are set but undocumented as extension hooks; the ChatWithThreads story keeps a stale replies count on the main conversation after a send (update message.replies.count in the send handler or note it in the story).

[pratikbuilds]

Thanks for the review. Here's what happened to each point.

Fixed

1. The sentId doc was wrong under stick (minor)

• The fix: rather than qualifying the doc, the Conversation engine (feat(conversation): add Conversation and its scroll anchoring #114) now ignores a sentId that matches none of its messages, under both policies. The doc now says exactly that.

2. Nits

• The labels.log doc now says it's used when neither aria-label nor aria-labelledby is given.
• data-thread-parent and data-thread-divider are documented as styling hooks.
• The reply count in the story now updates after a send. The replies live in the chat, and the count under the parent comes from them.

Not changed, and why

• A slot for loading earlier replies inside a thread: left as the follow-up you filed. It needs the thread to run useHistoryWindow itself.

Commit: docs(conversation): correct ConversationThread docs and story count

[TheGreatAxios]

Review · Approve

Adds ConversationThread. Scroll policy and sent id pass through, the log is named, and history and the map stay with the host.

Findings

No findings.

[pratikbuilds]

Round 3

No new findings on this PR. It is rebased onto the updated PR below; its own diff is unchanged.

bun run check and dep-guard pass on every branch of the stack, and the full e2e suite passes at the top of the stack (163/163, including the stories axe sweep). Each behaviour fix comes with a test that fails without it; the forwardRef tests can only guard, since the suite runs on React 19.