[Fix] Restore subtask approvals when users return to tasks

[zoomote]

​Created by Roomote. Follow up by mentioning @roomote, in the web UI, or in Discord.

What changed

• Persist validated new_task and finishTask actions while they await approval, then restore the executable action instead of a generic resume prompt.
• Give queued lifecycle feedback priority over auto-approval and keep it claimed until its history row is saved successfully.
• Reject stale restored actions before lifecycle side effects and at atomic commit boundaries.
• Add direct branch coverage for pending-action replay, queue claims and retries, provider metadata transitions, native approval feedback, and history schemas, alongside the VS Code e2e regression.

Why this change was made

Issue #1223 showed that leaving and returning to subtask workflows replaced approval controls with Continue or Start New Task. It also exposed a race where auto-approved completion could discard queued feedback. This work is tracked under #355 and coordinates with the existing task-lifecycle roadmap.

Impact

Users can return to pending subtask creation or completion approvals and continue the intended workflow. Queued feedback is retained and processed before automatic completion, including across transient history-write failures.

Related PRs

• Documentation: [Docs] Explain restored subtask approvals Zoo-Code-Docs#41

Closes #1223

[codecov]

Codecov Report

❌ Patch coverage is 82.03593% with 30 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/core/task/Task.ts	85.56%	5 Missing and 9 partials ⚠️
.../core/assistant-message/presentAssistantMessage.ts	20.00%	2 Missing and 6 partials ⚠️
src/core/webview/ClineProvider.ts	78.57%	2 Missing and 4 partials ⚠️
src/core/tools/AttemptCompletionTool.ts	84.61%	0 Missing and 2 partials ⚠️

📢 Thoughts on this report? Let us know!