wenjin272 opened a new issue, #1231: URL: https://github.com/apache/flink-agents/issues/1231
Parent: #1225 ### Problem and scope The YAML page mixes declarative schema reference, tool behavior, and maintainer implementation details. Tool parallelism guidance also exposes internal scheduling details instead of the user contract. #### Scope - [ ] Describe YAML as a declarative Agent orchestration API using triggers and references; clazz/function/type select implementations, code lives in Java/Python, and prompts may be defined inline. - [ ] Explain that Prompt text/messages require exactly one non-empty alternative, with validation failure rather than precedence when both are supplied. - [ ] Use consistent Required/Optional labels and complete conditional requirements, including parameter_types for Java tools. - [ ] Keep injected_args shape, sources, defaults, and a minimal example in YAML. Put injection motivation, runtime source semantics, Java annotations, and conflict rules in Tool Use. - [ ] State before alias tables that aliases cover built-ins; custom providers use fully qualified class names. - [ ] Move schema generation, Pydantic ground truth, copied skill schemas, and parity-testing guidance to contributor material. Clearly distinguish schema validation from reference/runtime/external dependency validation. - [ ] Explain parallel tool calls using enablement, defaults, and concurrency limits; coordinate concise configuration descriptions with Improve consistency, Action State Store, and configuration guidance. Preserve the constraint that calls must be independent and cannot depend on another call's completion, and avoid promising overlap or ordering. Remove unnecessary worker/continuation/slot implementation details. #### Coordination and acceptance Use #1227's YAML/language distinctions and #1229's Resource model. Coordinate remote Skills fields with #1230 and provider naming with Reorganize Chat Models, Chat Messages, and provider documentation. YAML and Tool Use must link to one authoritative explanation per concept, with valid Java/Python/YAML examples and consistent option defaults. #### Review coverage DOC-034, DOC-035, DOC-036, DOC-037, DOC-040, DOC-041, DOC-050. 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]
