Roos-fs-ZIP

Currently, the system updates each field of a task and its checklist via separate API calls. This leads to multiple requests being sent when a user fills out the checklist and updates the task status.

To improve efficiency and UX, we need a new API endpoint that allows the frontend to submit the entire checklist and the task status in a single request once the user finishes filling in the checklist.

Key reasons:

• Reduce the number of API calls by batching checklist updates and task status into one.
• Improve performance and consistency when saving task data.
• Ensure the new endpoint is backward-compatible or does not interfere with existing endpoints.
• first steop to impliment the offline mode

Acceptance Criteria:

• A new API endpoint (e.g., PUT /tasks/:id/checklist) is created.
• It accepts:
  --Full checklist data (array of items with completion state)
  --Task status (e.g., "in progress", "done", etc.)
  --The endpoint updates the task and its checklist in a single transaction.
  -- Proper validation and error handling are in place.
• API documentation is updated.