5 Commits

Include renames

Author	SHA1	Message	Date
jpmschweitzerandClaude Opus 4.8	a2437b0720	unify boxed conversation-card interior padding (T-282) ... Bordered cards (tool / Agent calls) used 10px vertical interior padding while stripe cards (you / claude) used 8, so a collapsed tool/Agent card read chunkier — taller box and more trailing space — than its neighbours in the conversation log. Match the bordered variant's vertical padding to the stripe variant (8) so boxed cards share one rhythm. Box-to-box inter-card margin is unchanged (a uniform 14). Regenerated the merged-card golden. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-08 17:42:01 +02:00
jpmschweitzerandClaude Opus 4.8	9a8f8641f7	merge successful tool call + result into one card (T-262) ... A successful tool call now renders as a single merged card instead of a separate call card + result card: - ConversationCard gains a trailing header status slot (success check / error cross, semantics-labelled) and optional labelled extra body segments (P1 + P2 — reused by T-263's Agent card). - conversation_view builds a reverse toolUseId→result lookup, folds a successful result into its call card as a colorized ClideCodeBlock (Read → file grammar, Bash → shell, else text), and suppresses the standalone success result in _visibleItems. Errors stay a separate prominent red card, now with a matching red header mark (note C). - Suppression happens before grouping, so a merged success result is no longer a separate activity-cluster step (note D). Tests: card status-mark + segment coverage, merged-fold + language inference + in-flight/orphan/error cases, cluster non-double-count, and a golden for the merged card (collapsed + expanded + error). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-07 19:41:28 +02:00
jpmschweitzerandClaude	80401a3228	make conversation card actions keyboard-reachable ... The copy button and custom message actions only rendered on hover, so they were unreachable by keyboard or assistive tech. Keep them in the tree always — revealed via opacity on hover OR focus — and route each through ClideTappable (Tab traversal + Enter/Space activation) with a Semantics button label and onTap so AT can discover and invoke them. alwaysIncludeSemantics keeps them in the semantics tree while hidden. T-174. Co-Authored-By: Claude <noreply@anthropic.com>	2026-05-30 23:09:57 +02:00
jpmschweitzerandClaude Opus 4.7	de264e7141	flesh out the Claude prompt UX: options, stepper, collapse ... Builds on the in-composer prompt surface (D-78): - Permission prompts (T-175): Allow / Allow-and-don't-ask-again / Deny. "Don't ask again" appears only when the request carries a permission_suggestion and echoes it back as updatedPermissions. An optional note rides Deny as the message, or Allow as a follow-up user message (the protocol has no allow-with-message). - AskUserQuestion picker (T-176): a single question renders bare; 2-4 questions step one at a time (nav shows "N · Header", ✓ when answered) then a review/confirm screen. Each question offers an "Other" free-text choice and a per-choice note; multi-select joins labels. A "chat instead" escape denies the prompt so the user can type freely. On submit the answer is echoed into the log, since the card is ephemeral. - Collapsed tool cards (T-177): multi-line tool_use / tool_result start collapsed behind a one-line summary; one-line output renders inline. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-25 09:30:50 +02:00
jpmschweitzerandClaude Opus 4.7	e672f1a77b	render every conversation turn through one card primitive ... The Claude pane's conversation view hand-rolled a separate card layout per message kind (user/assistant/thinking/tool-use/tool-result), so any shared chrome had to be added five times. ConversationCard is one template with three variants (stripe/bordered/bare) that wires the chrome once: a copy button revealed on hover (yielding the turn's raw text), an always-visible collapse/expand caret for collapsible turns, and an extensible MessageAction list. It's decoupled from ConversationItem — the view maps each item to (variant, accent, label, body, copyText, actions) — so the typed event cards coming with the stream-json work reuse the same chrome with a different body. T-173. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-24 19:10:02 +02:00