## 问题描述
Chatflow的"workflow_started"、"node_started"等workflow事件实体类缺少conversation_id字段。
直接调用dify的HTTP接口能够返回conversation_id,但SDK中只有BaseMessageEvent的子类包含该字段,
而BaseWorkflowEvent的子类缺失,导致前几个SSE事件无法获取conversation_id。

## 修复内容
- 在BaseWorkflowEvent基类中添加conversation_id字段,使其与BaseMessageEvent保持一致
- 所有继承BaseWorkflowEvent的事件类(WorkflowStartedEvent, NodeStartedEvent, NodeFinishedEvent等)
  现在都可以获取conversation_id

## 验证
- 已验证Dify HTTP API在chatflow模式下返回的workflow事件确实包含conversation_id字段
- 代码成功编译通过(mvn clean compile)
- 与BaseMessageEvent保持一致的设计

Fixes imfangs#145

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Fixes imfangs#146

The builtInMetadata API endpoint returns a JSON object ({"result": "success"})
instead of a plain string. This was causing a MismatchedInputException:
"Cannot deserialize value of type java.lang.String from Object value".

Changed the return type from String to SimpleResponse in both the interface
and implementation to properly handle the API response.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

…data-response-type

fix: Change builtInMetadata return type from String to SimpleResponse

- Fix builtInMetadata return type from String to SimpleResponse (imfangs#146)
- Add conversation_id field to BaseWorkflowEvent (imfangs#145)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

- add workflow_id support for Chatflow requests (imfangs#151)
- improve workflow event compatibility for workflow_id
- build: ensure Lombok annotation processing on newer JDKs

…mfangs#158)

- Add node_retry event support for Workflow and Chatflow streaming
- Add text_to_speech, more_like_this, sensitive_word_avoidance to AppParametersResponse
- Add workflow_file_upload_limit to SystemParameters
- Bump version to 1.2.6

…s#161)

- 引入 CHAT_TERMINAL_EVENTS 和 WORKFLOW_TERMINAL_EVENTS 常量集合
- 修改 processStreamLine 方法参数以支持动态终止事件判断
- 为聊天、补全、工作流等不同场景配置相应的终止事件类型
- 重构事件处理逻辑，统一通过枚举集合判断流式读取终止条件
- 移除硬编码的特定事件判断，提高代码可维护性
- 优化不同 Dify 应用类型的流式响应处理策略

Add doc_type, doc_metadata, summary_index_status, and need_summary fields
to align with the latest Dify API response for document detail endpoint.