fix: make task command required

[branchseer]

Summary

This change makes the command field mandatory in task configurations within vite-task.json. Previously, tasks could omit the command and fall back to a corresponding script defined in package.json. This change simplifies the configuration model by requiring explicit command definitions.

Key Changes

• Made command field required: Changed UserTaskConfig.command from Option<Box<str>> to Box<str>, making it a required field during deserialization
• Removed fallback logic: Eliminated the fallback mechanism that would use package.json scripts when a task command was omitted
• Removed error variants: Deleted ResolveTaskConfigError::CommandConflict and ResolveTaskConfigError::NoCommand as they are no longer needed
• Simplified task resolution: Updated ResolvedTaskConfig::resolve() to only accept user config and package directory, removing the package_json_script parameter
• Updated test fixtures: Modified all test fixtures to explicitly define commands in vite-task.json instead of relying on package.json scripts
• Updated documentation: Modified TypeScript type definitions and CLAUDE.md to reflect that command is now required

Implementation Details

• Tasks defined in vite-task.json must now include an explicit command field
• Package.json scripts are no longer used as fallbacks for task commands
• The configuration is now more explicit and reduces ambiguity about which command will be executed
• All existing test fixtures were updated to comply with the new requirement

https://claude.ai/code/session_01LMFoqFGF6abfJ3WuSeEoRk