Description

The specification should clarify the expected behavior when a message is sent with a taskId but without a contextId.

Questions to Address

• If a message is sent without a contextId but with a taskId, is the contextId implied?
• Or is this considered an error condition?

Suggested Action

Add clarification to the specification documentation regarding:

1. Whether contextId is automatically inferred from the taskId
2. The validation rules for message context parameters
3. Error handling expectations for this scenario