wenjin272 opened a new issue, #1232: URL: https://github.com/apache/flink-agents/issues/1232
Parent: #1225 ### Problem and scope Chat-model documentation mixes the framework message model with provider-specific capabilities and does not consistently expose all resource declaration entry points. #### Scope - [ ] Introduce connection/setup concepts before annotation, programmatic Agent/environment, and YAML declaration entry points. - [ ] Introduce ChatMessage, roles, plain-text factories, text/getText(), and relevant fields before advanced content/media blocks. - [ ] Explain the current framework block types, source kinds, media_type, and serialization contract. Keep provider-specific block/source/media-type support and model restrictions in provider sections. - [ ] Put a visible capability warning before the first multimodal example: representable content does not imply provider/model support. Verify the support matrix for 0.4, including the distinction between OpenAI Chat Completions and Responses. - [ ] Move framework-wide multimodal explanations out of OpenAI-specific sections; retain conversion and provider limits there. - [ ] Use `DashScope (Alibaba Cloud Model Studio)` consistently across chat, embedding, YAML, and FAQ, matching the delivered public API and migration policy. - [ ] Scope Azure AI Inference migration instructions to affected old-integration users upgrading from 0.2.x/0.3.x to 0.4.x, distinguishing Azure OpenAI and fresh installations. #### Coordination and acceptance Follow #1226's resource/provider grouping; coordinate aliases with #1231. Related API work: #1195 (bytes factories), #1196 (DashScope naming). Document current supported behavior, verify representative snippets and links, and distinguish framework contracts from provider/model capability restrictions. #### Review coverage DOC-011, DOC-042, DOC-043, DOC-044, DOC-045, DOC-046, DOC-047. These are traceability identifiers; the full actionable scope is described above. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
