fix(ui): preserve other pending answers on needs-input submit

[emrahzunicaplab]

Linked issue

Closes #622

Summary of changes

renderActionItems fully rebuilds the action-required panel's DOM after any
question submit (container.innerHTML = ...), so submitting one question in
a pending_questions batch wiped the .selected state and free-text drafts
on sibling, un-submitted questions — the only place that state lived.

Added a small client-side draft store (taskQuestionDrafts) in
src/ui/static/modules/actions.js that records each un-submitted
selection/free-text as the user makes it, and re-applies it whenever
renderTaskQuestionsItem repaints. The draft for a question is cleared once
the server confirms it's answered. No API or backend changes — this keeps
the existing per-question submit/resume contract documented in
PRD-029 (pending_questions[]: "mark answered per question; move when all
done"), rather than moving to a single "Submit all" action.

Screenshots / recordings

Before/after recording: on main, submitting one question in the 4-question batch wipes the in-progress selections on the other pending questions; on this branch, sibling selections/drafts are preserved across submits until each question is answered.

Before.mp4

After.mp4

Testing notes

Repro'd with a seeded needs-input task carrying 4 pending_questions
(extensions.runner.pending_questions) against a local dotbot serve
instance:

1. Open the action-required panel — 4 questions shown.
2. Select an option on Q2 and Q3 (don't submit).
3. Click "Submit Q1".
4. After the panel re-renders (~1.5s), Q2/Q3 selections are preserved —
   previously they were wiped.
5. Continue submitting Q2 → Q3 → Q4; panel correctly resolves to
   "No pending actions" once the last question is answered.

Checklist

• Linked issue exists
• Follows the contribution guide

[Copilot]

Pull request overview

Fixes the UI behavior where submitting one question in a pending_questions batch causes the action panel to fully re-render and lose unsubmitted selections/free-text drafts on sibling questions. This stays entirely client-side by persisting per-question drafts in module state and re-applying them on re-render.

Changes:

• Added an in-memory draft store for task-level batch questions (taskQuestionDrafts) keyed by task/question id.
• Updated renderTaskQuestionsItem to restore option selection and free-text from the draft store on every paint.
• Updated action handlers to record draft state on option selection / free-text input, and clear it once a question is successfully submitted.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.