Add type for RooCodeEventName.TaskSpawned

[mrubens]

Important

Add TaskSpawned event type to TaskProviderEvents and update tests to verify its emission, incrementing version to 1.62.0.

• Behavior:
  • Add TaskSpawned event type to TaskProviderEvents in task.ts.
  • Update newTaskTool.spec.ts to verify taskSpawned event emission with mock-subtask-id.
• Versioning:
  • Increment version to 1.62.0 in package.metadata.json.

^{This description was created by for 09c3ff3. You can customize this summary. It will automatically update as commits are pushed.}

[roomote]

Thank you for your contribution! I've reviewed the changes and found a critical type mismatch issue that needs attention.

Critical Issue

There's a type inconsistency with the TaskSpawned event across the codebase:

1. In packages/types/src/events.ts line 70: The Zod schema defines it as z.tuple([z.string(), z.string()]) expecting 2 string parameters
2. In packages/types/src/task.ts lines 62 and 116: The TypeScript types define it as [taskId: string] expecting 1 string parameter
3. In src/core/tools/newTaskTool.ts line 139: The actual usage emits only 1 parameter: cline.emit(RooCodeEventName.TaskSpawned, newCline.taskId)

This mismatch will cause runtime validation errors when the event is emitted. The Zod schema in events.ts should be updated to match the TypeScript types and actual usage:

[RooCodeEventName.TaskSpawned]: z.tuple([z.string()]),  // Only 1 parameter, not 2

Other Observations

✅ The test update correctly verifies the event emission with the expected task ID
✅ The version bump from 1.61.0 to 1.62.0 is appropriate for adding a new event type

Could you please fix the Zod schema to align with the TypeScript types and actual usage?