feat(web): group consecutive tool-use cards

[junxin367]

Summary

• group consecutive root-level execution tool cards in web chat into one collapsible card
• keep approval / AskUserQuestion / request_user_input cards standalone and use them as grouping boundaries
• auto-load older pages when expanding an oldest incomplete group, and add regression coverage for grouping/runtime/thread behavior

Reason

• reduce chat noise from tool-heavy sessions while preserving full timeline access and detail drill-down

Scope

• web-only visible projection and grouped tool card UI
• no hub API, persistence, or pagination semantic changes

Test

• cd web && bun run test -- src/chat/toolGroups.test.ts src/components/ToolCard/ToolGroupCard.test.tsx src/components/AssistantChat/HappyThread.test.tsx
• cd web && bun run typecheck

Risk / Rollback

• Risk: grouped rendering boundaries and oldest-history hydration behavior in session chat
• Rollback: revert this PR to restore per-tool card rendering

Links

• none

Reviewer Notes

• focus on grouping eligibility and summary extraction in web/src/chat/toolGroups.ts
• focus on incomplete-history hydration and stable open-state behavior in ToolGroupCard and HappyThread
• UI-only change; no browser screenshot captured in this CLI pass

[github-actions]

Review mode: initial

Findings

• [Major] needsOlderHistory is only set when the grouped run starts at index 0, so a tool group that is the oldest visible group but follows a text/event block never auto-loads older pages when expanded. That breaks the promised oldest-incomplete-group hydration on pages that begin with non-tool content. web/src/chat/toolGroups.ts:254-265
  Suggested fix:

  let sawGroup = false
  
  for (let index = 0; index < blocks.length; index += 1) {
      ...
      const needsOlderHistory = options.hasMoreMessages && !sawGroup
      sawGroup = true
      ...
  }

Summary

• Review mode: initial. One blocking behavior gap found; no other issues confirmed in the diff.

Testing

• Not run (bun is unavailable in this environment).

HAPI Bot

[github-actions]

[Major] needsOlderHistory is only set when the grouped run starts at index 0, so a tool group that is the oldest visible group but follows a text/event block never auto-loads older pages when expanded. That breaks the promised oldest-incomplete-group hydration on pages that begin with non-tool content.

Suggested fix:

let sawGroup = false

for (let index = 0; index < blocks.length; index += 1) {
    ...
    const needsOlderHistory = options.hasMoreMessages && !sawGroup
    sawGroup = true
    ...
}

[junxin367]

Fixed in cd6f0b5. needsOlderHistory now follows the first visible grouped run instead of index === 0, so oldest visible groups still hydrate when leading visible blocks are text/event content. Added regression coverage in web/src/chat/toolGroups.test.ts.

[github-actions]

Review mode: follow-up after new commits

Findings

• [Major] Incomplete tool groups can stop hydrating after the first older-page request. ToolGroupCard starts a load, but the same effect depends on ctx.isLoadingMoreMessages; when the shared loader flips that flag, React runs the cleanup and marks the in-flight request as cancelled. The eventual promise resolution then cannot clear isHydratingHistory, and the next effect pass returns early on isHydratingHistory, so a multi-page incomplete group can stay stuck instead of loading until its boundary is complete. Evidence: web/src/components/ToolCard/ToolGroupCard.tsx:174.
  Suggested fix:

  useEffect(() => {
      if (!open || !props.block.needsOlderHistory || historyExhausted) return
      if (!ctx.hasMoreMessages) {
          setHistoryExhausted(true)
          return
      }
  
      let cancelled = false
      setIsHydratingHistory(true)
      void ctx.loadOlderMessagesPreservingScroll()
          .then((loaded) => {
              if (cancelled) return
              setIsHydratingHistory(false)
              if (!loaded) setHistoryExhausted(true)
          })
          .catch(() => {
              if (cancelled) return
              setIsHydratingHistory(false)
              setHistoryExhausted(true)
          })
  
      return () => {
          cancelled = true
      }
  }, [
      open,
      props.block,
      ctx.hasMoreMessages,
      ctx.loadOlderMessagesPreservingScroll,
      historyExhausted,
  ])

Summary

• Review mode: follow-up after new commits. The prior bot finding about marking the oldest visible group appears addressed, but grouped expansion still has a remaining hydration regression for incomplete history.

Testing

• Not run (automation; bun is unavailable in this environment: /bin/bash: bun: command not found).

HAPI Bot

[github-actions]

[Major] Incomplete tool groups can stop hydrating after the first older-page request. This effect starts a load, but it also depends on ctx.isLoadingMoreMessages; when the shared loader flips that flag, React runs the cleanup and marks the in-flight request as cancelled. The eventual promise resolution then cannot clear isHydratingHistory, and the next effect pass returns early here, so a multi-page incomplete group can stay stuck instead of loading until its boundary is complete.

Suggested fix:

useEffect(() => {
    if (!open || !props.block.needsOlderHistory || historyExhausted) return
    if (!ctx.hasMoreMessages) {
        setHistoryExhausted(true)
        return
    }

    let cancelled = false
    setIsHydratingHistory(true)
    void ctx.loadOlderMessagesPreservingScroll()
        .then((loaded) => {
            if (cancelled) return
            setIsHydratingHistory(false)
            if (!loaded) setHistoryExhausted(true)
        })
        .catch(() => {
            if (cancelled) return
            setIsHydratingHistory(false)
            setHistoryExhausted(true)
        })

    return () => {
        cancelled = true
    }
}, [
    open,
    props.block,
    ctx.hasMoreMessages,
    ctx.loadOlderMessagesPreservingScroll,
    historyExhausted,
])

[junxin367]

Fixed in e64ec84. Tool-group older-history chaining no longer depends on the shared isLoadingMoreMessages flag; ToolGroupCard now tracks hydration runs internally so in-flight loads are not cancelled by intermediate provider state flips, and it can continue loading multiple older pages until the boundary is complete or history is exhausted. Added regression coverage for multi-page hydration in web/src/components/ToolCard/ToolGroupCard.test.tsx.