feat: show the working indicator in ChatPane (member DMs, split panes)

[CrysisDeu]

Problem / Motivation

A running turn inside a ChatPane host — a Crew Members DM thread, a split pane in the session grid — is invisible between tool steps. The pane renders streamed text and tool rows, but during the gaps (thinking, tool execution, post-tool pauses) nothing on screen moves: a hard-working member looks stalled, and users cannot tell "working" from "dead".

Why it matters

The Crew Members page is the accountability surface for autonomous member activity; "is it doing anything right now" is the page's core question. The full chat page already answers it with the ghost-pose loading carousel — panes answering it with silence is an inconsistency users notice immediately after meeting the animation on the main page.

What changed (motivation → approach → change)

Goal: the same working signal in panes as on the chat page — without inventing a second visual vocabulary.

Approach: reuse, don't rebuild. ChatFooter (the 4-slot ghost-pose carousel, theme-swappable via themeBranding loader/loaderIcons) is self-contained and driven entirely by props, so ChatPane can host it directly.

• ChatPane.tsx: render ChatFooter inside the scroll container after the last message, fed from the pane's own per-slot stream state (selectSlotStreamState) — running shows the carousel, stopping/compacting show their existing states, active text streaming yields to the inline caret (ChatFooter's own algebra), idle renders nothing. Stop/regenerate chrome stays page-level.
• No new state, no backend, no new i18n strings; theme loader overrides now apply in panes for free.
• New isolated capture entry capture/chatpane-loader.html + capture/chatpane-loader.tsx (real ChatPane, warm-slot seeding through the same sseChatMessage/hydrateSlotMessages reducers the WS drives) and a state-asserted capture script scripts/capture-chatpane-loader.mjs.

Tests

ChatPane.workingLoader.test.tsx pins the wiring (ChatFooter's own suite covers its visibility algebra):

• tool_running → footer + carousel render in the pane
• idle → no footer at all
• active text streaming (fresh tick) → footer absent, the inline caret owns the signal

Manual verification

recorded from b824395 · feat/chatpane-ghost-loader · vite dev serving branch source, isolated capture entry capture/chatpane-loader.html with route-stubbed /api fixtures, state asserted before every frame · no live gateway

Stills: 01-running-dark · 02-idle-dark · 03-running-light

Gates: tsc -b clean, eslint clean, full frontend suite 27431 passed, full 19-check i18n suite PASS.

no linked issue: gap identified during the Crew Members animation design review with the maintainer in-session; no tracking issue exists.

[github-actions]

First Principles Review (Fable 5) — ✅ PASS

Premise-level review of b824395ae67744d08e0ac38266749e46a9f86d71 — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

All evidence is in. Both sibling transcript hosts carry their own signal (SideChat has three pulsing dots at SideChat.tsx:591-593; ChatEmbed keeps a header dot + "streaming" label), the capture apparatus follows a 372-script convention, and the ChatPane diff adds no new state or props — ChatFooter simply gains its second real consumer.

First-Principles-Verdict: PASS

Reuse at cause level: the pane hosts the page's existing ChatFooter unchanged, and every rider is the repo's established capture/test convention.

What this change ships

Intent: make a running turn visible inside ChatPane hosts (member DMs, split panes) between tool steps — an ADDITION.

1. Panes show the ghost-pose working carousel while a turn runs — justified
2. Panes show the existing stopping/compacting states — declared, inherent to the reused algebra
3. Theme loader/loaderIcons overrides now apply in panes — declared, free via reuse
4. Indicator also covers the pre-stream gap (paneSlot.running union) — declared in tests, same union the full page uses
5. New capture entry + state-asserted capture script — declared, matches 157 capture-entry / 372 capture-script siblings
6. Three stills + GIF committed under temp-screenshots/ — declared, matches the 569-file convention
7. New wiring test file — declared

No duplication: grep <ChatFooter finds exactly two production consumers (ChatPage.tsx:7997, ChatPane.tsx:724) of one component; no props were added to it, and the pane's inputs (streamState, running, paneSlot) all pre-existed. Grep <ChatMessageList finds three production hosts: SideChat already has its own dot indicator, leaving only app-sdk/ChatEmbed.tsx:257 with header-chrome-only signaling — outside the declared job (an app-embed surface, not the Crew Members accountability page), so not a point patch. The "nothing on screen moves" framing slightly overstates the framed-pane case (the header dot at ChatPane.tsx:655 pulses), but the in-flow gap the feature fills is real and the frameless member-DM host shows no header at all.

[FIRST-PRINCIPLES-REVIEWED] b824395

[github-actions]

Design Review (Fable 5) — ✅ PASS

Design-level review of b824395ae67744d08e0ac38266749e46a9f86d71 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

Design-Verdict: PASS

Straight reuse of the page's existing loader through its prop seam, fed by the pane's own slot state — the right shape, minimal surface.

Suggestions

• The footer-input derivation (lastRole / content-length-as-streamTick) is now duplicated verbatim between ChatPage.tsx:5826 and ChatPane.tsx:728-733; a shared selector/helper would keep the two hosts from drifting when the streaming-quiet heuristic next changes.

[DESIGN-REVIEWED] b824395

[github-actions]

UX Review (Fable 5) — ✅ PASS

UX-level review of b824395ae67744d08e0ac38266749e46a9f86d71 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

The diff is a small parity change: ChatPane (member DMs, split panes) now renders the same ChatFooter working indicator the full chat page already uses, with per-slot stream state driving it. Screenshots confirm the carousel renders correctly in dark and light, a stop affordance (red square) is present in the composer while running, and the idle state shows no residue. No new user-facing strings; existing i18n'd states ("Stopping…", "Compacting…") are wired through. ChatMessageList adds no competing indicator, and the footer already suppresses itself while text actively streams, so there is no double-cursor risk. Placement matches the chat page (inside the scroller, after the last message).

UX-Verdict: PASS

Straight parity port of the existing working indicator to panes — same component, same placement, per-slot state wired correctly, both themes verified.

[UX-REVIEWED] b824395

[github-actions]

Opus 4.8 Review — ✅ no blocking findings

Reviewed b824395ae67744d08e0ac38266749e46a9f86d71 — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] b824395

Verdict parsed from the review's SHA-scoped output markers for commit b824395ae67744d08e0ac38266749e46a9f86d71.

False positive or not applicable? A repository writer can comment:
/ai-review override fable b824395ae67744d08e0ac38266749e46a9f86d71: <one-sentence reason>

[github-actions]

GPT 5.6 Review — ✅ no blocking findings

GPT 5.6 completed its review of b824395ae67744d08e0ac38266749e46a9f86d71 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] b824395

False positive or not applicable? A repository writer can comment:
/ai-review override gpt b824395ae67744d08e0ac38266749e46a9f86d71: <one-sentence reason>

[CrysisDeu]

Disposition — GPT advisory finding (ChatPane.tsx:725, head 5c463d8): FIXED in b824395. The pane's footer now unions the stream-state signal with the slots-broadcast one — running={running || !!paneSlot?.running}, stopping likewise — matching what the full page gets from startLocalTurn + syncSlotRunningFromServer: the indicator shows in the pre-first-frame window after a send (and for Slack/cron-initiated turns), and a server-reported stopping is not missed. Pinned by a new test case (server running=true, stream still idle → footer renders).