Voice: Send button unresponsive or gives no feedback after Tap-to-Talk listening mode

[serge-ivo]

Summary

In the coder agent Co-pilot chat (CopilotView.tsx), after tapping "Tap to Talk" and entering listening mode, the green Send (tap-to-send) button is not reliably clickable — or it registers the click but gives no visual feedback, so the user can't tell whether it worked.

Steps to Reproduce

1. Open the Co-pilot chat and switch to Tap to talk.
2. Tap the chat to enter listening mode.
3. Tap the green Send button.
4. Nothing visible happens.

Expected Behavior

The Send button shows immediate visual feedback on tap (a pressed/active state), disables while the message is being sent/processed, then transitions to the next state.

Actual Behavior

The button appears to do nothing — or it silently starts processing with no status change, so the tap seems ignored.

Investigation Areas

• Click event propagation / interception: the floating voice status pill and the chat-thread tap handler (handleThreadTap) may intercept the tap; z-index/overlay could sit over the button.
• Disabled/hidden in listening mode: Send is disabled={!!voice.interim} — while a live interim transcript is showing, Send is disabled, which can read as "unresponsive".
• Missing feedback: no pressed/active state and no loading/disabled state while sendInstruction runs.

Priority

High — blocks the hands-free / co-pilot send flow.

[serge-ivo]

Fixed in f09db42. The Send button is now clickable in listening mode (disabled only while a reply is generating — summaryBusy, no longer on voice.interim), has an immediate pressed state (active:scale-95), swaps to a spinner while processing so a tap always shows it registered, and the input bar gets relative z-10 so nothing intercepts the tap over the status pill.