[turinglambdaai]

User impact

Older Windows Taskly builds could file tasks created in 生活 into 工作 because the quick-add RPC passed no list ID (#35). Fixing future submissions does not restore tasks already saved to the wrong list. It would be unsafe to auto-migrate them: Taskly cannot determine their originally intended destination.

Change

• Add a native Move to List / 移动到列表 submenu to each Windows task row context menu whenever other lists exist, matching the PRODUCT-SPEC and macOS interaction.
• Populate choices from the latest list snapshot (emoji + name), excluding the task's current list.
• Route the selected target ID to the existing backend update_task API; leave task text, due date/time, notes and completed flag untouched.
• Surface a localized statusTaskMoved message on success; report RPC errors without optimistic UI mutation.
• Document the manual recovery procedure for already-misfiled tasks.

Dependencies

Stacked on #35 (which in turn depends on #32). Merge in order #32 → #35 → this PR, then confirm the reduced diff and rerun final integrated acceptance.

QA before merge

• Windows native CI + packaged Product Acceptance pass on this branch.
• Right-click a legacy task under 工作 → 移动到列表 → 生活; verify it disappears from 工作, reappears in 生活, and survives relaunch.
• Verify due date/time, notes, completed state and title remain unchanged.
• Test from list and smart views, with only one list, plus Chinese/English labels and light/dark themes.
• Ensure no existing task is silently moved by upgrading.

No merge/release until all task-ownership and alignment checks pass.