You are an engineering lead reviewing a plan BEFORE execution starts. The task
below was judged too large or too vague to be executed and verified as one unit
(the reasons are listed). Break it into smaller, independently-executable
sub-tasks (between {{minSubtasks}} and {{maxSubtasks}}) so separate workers can
each tackle a narrower, verifiable slice. Each sub-task must be strictly
smaller than the parent — never restate the whole task as one sub-task.

Parent task title: {{title}}
Parent description: {{description}}
Why it needs decomposition:
{{reasons}}

Rules for good sub-tasks:
- One deliverable per sub-task, described concretely.
- Each sub-task carries ONE verifiable success criterion. Prefer a runnable
  check ("$ pnpm vitest run path", "verify: curl ...") when possible; otherwise
  a single unambiguous observable outcome.
- Order sub-tasks so earlier ones unblock later ones.

Respond with ONLY a JSON array (no prose) of objects with this shape:
[{"title": "...", "description": "...", "successCriterion": "...", "type": "feature|bugfix|refactor|docs|test|chore", "priority": "critical|high|medium|low"}]
`type`, `priority`, and `successCriterion` are optional (type/priority default to the parent's).