wenjin272 opened a new pull request, #1263:
URL: https://github.com/apache/flink-agents/pull/1263

   Linked issue: #1229
   
   ### Purpose of change
   
   The Create an Agent guides mix core concepts with implementation details and 
leave Java/Python authoring and Event serialization behavior unclear. This PR 
reorganizes Overview, Actions, and Events into a practical authoring guide and 
aligns references across Quickstart, YAML, memory, model calling, and 
operations documentation.
   
   - Define Events, Actions, and Resources in Overview, with a concise workflow 
example and shared Resource registration guidance.
   - Align Java/Python Action examples, introduce trigger conditions 
progressively, move detailed matching rules into a reference section, and 
explain async and durable execution together.
   - Explain Event construction, custom subclasses, built-in Actions, and typed 
payload restoration, distinguishing normal Java delivery, Python boundaries, 
and persisted Event replay.
   
   ### Tests
   
   - Hugo 0.124.1 build passed (73 pages); checked internal page and anchor 
links from all 19 changed pages.
   - Java/Python documentation example checks performed during the edits, 
including Event reconstruction, JSON round trips, and Java compilation against 
the rebuilt API with `--release 11`.
   - Eight focused Python async/durable runtime tests passed during the Actions 
update.
   - `git diff --check` passed.
   - Full Flink and cross-language end-to-end jobs were not run; this PR 
changes documentation only.
   
   ### API
   
   No public API or runtime behavior changes.
   
   ### Documentation
   
   - [ ] `doc-needed`
   - [ ] `doc-not-needed`
   - [x] `doc-included`
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   - [x] Yes
   - [ ] No
   
   Generated-by: Codex CLI 0.153.4 (GPT-6)
   


-- 
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]

Reply via email to