feat(web): add question tool support to web UI

[R44VC0RP]

Summary

Adds support for the question tool in the web UI, fixing #7599.

Changes:

• Enable QuestionTool in web client (removed CLI-only restriction)
• Add question state management to global-sync context
• Create QuestionPrompt component with tabbed multi-question support
• Position question prompt above input in dock area (popunder style)
• Add question rendering to share/web view
• Wire up question respond/reject handlers in DataProvider

Status

WIP - Core functionality is working but design refinements are still in progress:

• Fine-tune spacing and visual polish
• Ensure seamless connection between question prompt and input box

Testing

1. Start dev servers:
   • API: cd packages/opencode && bun dev -- serve --port 5555
   • Vite: cd packages/app && bun dev
2. Open http://localhost:3000
3. Trigger a question tool (e.g., ask the AI to ask you questions)

Fixes #7599

[github-actions]

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

1. Open an issue describing the bug/feature (if one doesn't exist)
2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

[github-actions]

The following comment was made by an LLM, it may be inaccurate:

Based on my search, I found one potentially related PR:

Related PR:

• feat: add ask_user tool for interactive user questions #6681 - feat: add ask_user tool for interactive user questions
  • feat: add ask_user tool for interactive user questions #6681
  • This PR adds the underlying ask_user tool functionality, which is what the current PR (feat(web): add question tool support to web UI #7732) is enabling in the web UI. Worth checking if they're aligned on implementation or if there's overlap in the question handling logic.

The current PR (#7732) appears to be focused on exposing/integrating question tool support in the web UI layer, while #6681 addresses the tool itself. They may be complementary rather than duplicates, but reviewing #6681 would ensure consistency in how questions are handled.

[adamdotdevin]

@R44VC0RP ohhhh, screenshots?

[R44VC0RP]

Ah @adamdotdevin sorry linked in issue:

#7599 (comment)

[mortimr]

Nice 👀 ! Maybe we should find a way to join forces #7653

[offlinehacker]

I have implemented it #7751 as part of message-part.ts, so it's actually part of conversation and looks the same as permission prompt or other prompts. I was not aware that you were working on it as well.