Jason(Zhe-You) Liu ab4da0b563 Java SDK: Declare a Dag's task graph with @Builder.Deps (#71189) ...

* Java SDK: Declare a Dag's task graph with @Builder.Deps

An annotated Dag class could name its tasks but not say how they connect,
so a Dag whose annotations carried everything else still needed a Python
Dag file for its graph. Declaring the graph by calling the tasks lets
javac check that each task is fed something its parameter accepts.

Bundle.register(Class) now also takes the @Builder.Dag class itself and
registers the Dag its generated builder builds, so there is still only one
name to keep in sync.

* Java SDK: Quote wired task ids as Java string literals

* Java SDK: Validate the @Builder.Deps class at compile time

* Java SDK: Reject task method names that clash with the wiring view

* Java SDK: Type a wired numeric input by its parameter's own type

* Java SDK: Register both the Dag and handlers of a class, unwrapping builder failures

* Java SDK: Reject a raw null wiring argument and test the recorder's guards

* Java SDK: Reword the native-Dag docs without em-dashes

* Java SDK: Drop Bundle tests that repeat existing coverage

* Java SDK: Require a @Builder.Deps class on every @Builder.Dag class

* Java SDK: Back the k8s test's stub tasks with task handlers

* Java SDK: Reject overloaded task and task-handler methods

* Java SDK: Fix the Dag examples a required wiring class invalidates

2026-10-06 10:55:35 +08:00

..

0001-mixed-lang-dag-interface.md

Java SDK: Honor TaskFlow arg bindings sent by the supervisor (#71188)

2026-09-25 13:27:58 +08:00

0002-native-dag-interface.md

Java SDK: Declare a Dag's task graph with @Builder.Deps (#71189)

2026-10-06 10:55:35 +08:00