API silently redirects tasks to Inbox when invalid projectId is provided

[evalor]

Description

When creating a task with a non-existent projectId, the API silently creates the task in the Inbox instead of returning an error. This behavior can lead to user confusion as tasks may end up in unexpected locations without any warning.

Steps to Reproduce

1. Call the create_task tool with an invalid/non-existent projectId
2. Observe that the API returns a success response
3. Check where the task was actually created

Expected Behavior

The API should either:

• Return an error indicating that the specified project/list does not exist
• Return a response that clearly indicates the task was redirected to the Inbox

Actual Behavior

• The API returns a success response without any error or warning
• The task is silently created in the Inbox instead of the specified project
• No indication is given that the projectId was invalid

Impact

• Users may not realize their tasks are being placed in the wrong location
• This could lead to missed tasks or organizational issues
• The silent failure makes debugging difficult

Suggested Fix

1. Option A (Preferred): Validate projectId before creating the task and return an error if it doesn't exist
2. Option B: Include a warning or redirect notice in the response when a task is moved to Inbox due to invalid projectId

Environment

• MCP Server Version: Dida365 MCP Server
• Test Date: 2025-11-26

Related Test Case

This issue was discovered during test scenario E-3: Invalid Project ID Handling in the comprehensive MCP server testing.

Test Scenario Details

Test ID: E-3
Category: Error Handling - Parameter Errors
Test Request: Create a task in a non-existent project/list

Test Steps:

1. User request: "Create a task in a project that doesn't exist"
2. MCP tool called: create_task with projectId="non_existent_id_12345"
3. API Response: Success (HTTP 200)
4. Task location: Inbox (not the specified project)

Expected Result:

• API should return an error message indicating the project does not exist
• Or return a clear warning that the task was redirected

Actual Result:

• API returned success with no error or warning
• Task was silently created in Inbox
• User received no indication of the redirect

Related Test Scenarios

Test ID	Scenario	Status	Note
E-3	Invalid projectId handling	⚠️ Issue Found	This issue
E-4	Non-existent taskId handling	⚠️ Similar Issue	API returns success for non-existent task operations

Additional Context

This behavior was consistently reproducible during the full MCP server test suite execution on 2025-11-26. The same silent-failure pattern was observed in E-4 (completing non-existent tasks), suggesting this may be a broader API validation issue rather than an isolated case.

[evalor]

We are starting to deal with this problem.