Add UI for Context Chat Multi: batch question input and output

[MichelleAntunes]

UI implementation for #637.

Problem

Context Chat currently answers one question per task. For workflows that need answers to a fixed batch of related questions against the same knowledge base, this means submitting each question as a separate task and manually reassembling the results.

Solution

Adds the Assistant UI for the new "Context Chat Multi" task type (backend: nextcloud/context_chat_backend#351). Users can add/remove question fields (currently capped at 20, read from the backend's configured limit rather than hardcoded), and the output shows one block per question with its answer and sources, reusing existing output components where possible.

Changes

• src/components/ContextChat/ContextChatMultiInputForm.vue: new input form, add/remove question fields, starts with the 2-question minimum
• src/components/ContextChat/ContextChatMultiOutputForm.vue: new output form, one block per question (question, answer, sources)
• src/components/AssistantFormInputs.vue / AssistantFormOutputs.vue: register the new components for the Multi task type
• src/components/TaskListItem.vue: show the first question and remaining count in the task list sidebar for Multi tasks

Testing

Tested end-to-end on a real Nextcloud instance with the companion backend branch: submitted a batch of questions against real indexed documents and confirmed the UI returns correctly answered, source-attributed results for each question.

Companion PR

This is the UI half of the feature. Backend: nextcloud/context_chat_backend#351

🤖 AI (if applicable)

• The content of this PR was partly or fully generated using AI

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 39c3812e-8237-4274-88eb-fb4239a94609

📥 Commits

Reviewing files that changed from the base of the PR and between 3ee44bb and bb8d73f.

📒 Files selected for processing (5)

• src/components/AssistantFormInputs.vue
• src/components/AssistantFormOutputs.vue
• src/components/ContextChat/ContextChatMultiInputForm.vue
• src/components/ContextChat/ContextChatMultiOutputForm.vue
• src/components/TaskListItem.vue

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

Adds support for context_chat:context_chat_multi across assistant input and output forms. The input form manages multiple questions, selective context, source or provider scopes, provider loading, and serialized scope metadata. The output form displays each question, answer, and referenced source. Task-list entries now show the first question and the count of additional questions.

Merge Risk: ⚪ Minimal · up to bb8d7

The multi-question UI change has no remaining actionable merge risk.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The description clearly explains the Context Chat Multi UI feature, its input and output components, task list updates, testing, and companion backend work.
Title check	✅ Passed	The title clearly and concisely identifies the main change: adding UI support for Context Chat Multi batch question input and output.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[julien-nc]

Hi, thanks for the PR! Not sure we want 2 task types. We are discussing in the team how it's best to move forward.

[MichelleAntunes]

@julien-nc Thanks for the feedback! No worries at all — happy to adjust once you've settled on a direction. Let me know if you need any more context on the current approach in the meantime.