[ENHANCEMENT] thinking timer

[5shekel]

Problem (one or two sentences)

user often only has the thinking timer (Thinking 1s) as a progress bar/indicator
i noticed it doesnt seem to work in "user clock" like here, it took 10 seconds in userclock and (probably) 1 second in progclock

Context (who is affected and when)

happens whenever roo is thinking

Desired behavior (conceptual, not technical)

finding balanced between reporting actully ap call and perceived time by user.

Constraints / preferences (optional)

No response

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

[roomote]

I've analyzed this issue and here's my proposed implementation plan:

Root Cause Analysis

The "Thinking" timer in ReasoningBlock.tsx currently initializes its start time using Date.now() when the component mounts (line 23). This creates a disconnect between:

1. What the timer shows: Time since the ReasoningBlock component rendered
2. What users perceive: Time since they submitted their message (user-clock)

The flow is:

1. User sends message
2. api_req_started message is created with timestamp
3. API request is made to the model
4. When reasoning content starts streaming, a reasoning message is created
5. ReasoningBlock renders and starts its timer from Date.now() - this is the problem

The gap between steps 2-4 (waiting for the model to respond) is not captured by the timer.

Proposed Solution

Modify the ReasoningBlock component to use the most recent api_req_started message's timestamp as the start time, rather than the component mount time:

1. Pass the API request start time to ReasoningBlock: Update ChatRow.tsx to find the most recent api_req_started message timestamp and pass it as a new apiRequestStartTime prop to ReasoningBlock
2. Update ReasoningBlock to use this timestamp: Modify the timer calculation to use the passed apiRequestStartTime instead of Date.now() at mount
3. Fallback behavior: If no api_req_started timestamp is available, fall back to the current behavior

Files to modify:

• webview-ui/src/components/chat/ChatRow.tsx - Pass the api_req_started timestamp to ReasoningBlock
• webview-ui/src/components/chat/ReasoningBlock.tsx - Use the passed timestamp for timer calculation

This approach will show users the actual elapsed time from when the API request started, which better reflects their perceived wait time.

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.