wenjin272 opened a new issue, #1230: URL: https://github.com/apache/flink-agents/issues/1230
Parent: #1225 ### Problem and scope ReAct guidance omits important configuration/default behavior, while remote Skills guidance mixes the current contract with migration language. #### Scope - [ ] Explain required chat-model configuration, prompt guidance, and optional tools/Skills. Do not imply automatic Vector Store retrieval without an implemented capability. - [ ] Describe output behavior when no output schema is configured: verify and document whether instructions, JSON parsing/validation, or type conversion occur, and how final message text becomes output. - [ ] Document the delivered ReAct Skills constructor API and its interaction with descriptor configuration and allowed commands. - [ ] Describe HTTPS as the default for remote Skills and explicit `url_sources` / `allow_insecure_http` opt-in for trusted development networks, without historical compatibility framing. - [ ] Distinguish unpinned HTTPS transport guarantees from digest-pinned content. Do not imply dynamic runtime reload. - [ ] Document Python use of classpath repositories and Java use of Python package repositories as supported by the delivered implementation, including packaging/runtime requirements and linked examples. #### Coordination and acceptance Follow #1226's structure and #1229's Resource model; coordinate YAML field reference with Clarify YAML reference and Tool Use responsibilities. Related API work: #1193 and #1194. Verify defaults, source-loading examples, and security-related option descriptions against current code. This issue covers user guidance; implementation remains with the API issues. #### Review coverage DOC-032, DOC-033, DOC-038, DOC-039. 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]
