Updated CustomTask to use nested objects for category, frequency,
priority, and status instead of strings to match the API's actual
response format after recent serializer changes.
Changes:
- category: String → TaskCategory?
- Added frequency: TaskFrequency
- priority: String → TaskPriority
- status: String? → TaskStatus?
- Added next_scheduled_date field
- Added completion_count field
This fixes the JSON parsing error when creating/updating tasks via
the iOS and Android apps, which was caused by the API returning
nested objects like {"id": 21, "name": "Flooring"} but the model
expecting simple strings.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
07dfd55507