wenjin272 opened a new issue, #1233: URL: https://github.com/apache/flink-agents/issues/1233
Parent: #1225 ### Problem and scope The Model Routing quick start introduces judge prerequisites before a rule-based example, and the regex and result-handling contracts need clearer user guidance. #### Scope - [ ] Make the rule-based quick start require only what its example uses; introduce the judge model in the LLM Judge section. - [ ] Explain the current regex engine, case flags, substring versus whole-string matching, and Java string escaping. Verify java.util.regex.Pattern / CASE_INSENSITIVE / Matcher.find behavior against the delivered implementation. - [ ] Document the actual annotation, programmatic, YAML, and Python entry points supported in 0.4, with explicit limits for unavailable paths. - [ ] Explain candidate selection, abstain/default behavior, and invalid-result handling consistently across strategies, using the agreed runtime contract. #### Coordination and acceptance Follow #1226's Calling LLMs structure. Related work: #1133, #1062, and #1197. Keep this as the focused documentation deliverable linked to the existing routing tracker. Verify quick-start dependencies, regex examples, and capability/result tables against current code; avoid presenting proposed APIs as released features. #### Review coverage DOC-048, DOC-049. 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]
