test(coding-agent): use current task batch schema

[wolfiesch]

What

Update the task async-fallback regression input to the current { context, tasks[] } batch shape.

Why

task.batch is enabled by default, but this test still used the removed id, description, and assignment fields. Validation therefore returned Missing tasks before the test could exercise the synchronous fallback. This changes only the test input; runtime behavior is unchanged.

Testing

• bun test packages/coding-agent/test/tools/task-async-fallback.test.ts
• bun --cwd=packages/coding-agent run check

---

• bun check passes
• Tested locally
• CHANGELOG updated (if user-facing; not applicable)

[Copilot]

Pull request overview

Updates the task.async-fallback regression test in packages/coding-agent/ to use the current task.batch call shape ({ context, tasks[] }), so the test can reach and validate the synchronous fallback path when async.enabled is on but no asyncJobManager is present.

Changes:

• Replaced legacy task input fields (id, description, assignment) with the batch schema’s context plus tasks[] items ({ name, agent, task }).
• Ensured the test input satisfies current batch validation requirements (non-empty context, non-empty tasks[]).

---

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

[roboomp]

P0 / LGTM: the one-line test input change matches the current { context, tasks[] } batch schema in TaskParams, and it still reaches the sync fallback path via execution-time discoverAgents re-discovery.

No inline findings. Verification: bun --cwd=packages/coding-agent run check passed. bun test packages/coding-agent/test/tools/task-async-fallback.test.ts could not enter the test body in this clean worktree because packages/coding-agent/src/export/html/tool-views.generated.js has not been generated; that appears unrelated to this diff.

Thanks for keeping the regression aligned with the current task tool contract.