Break the new dag_bundle_name docs only at sentence ends

Co-Authored-By: Claude <noreply@anthropic.com>

Author: jason810496

airflow-core/docs/authoring-and-scheduling/language-sdks/go.rst

@@ -207,7 +207,10 @@ then register the coordinator and route the queue to it in ``airflow.cfg`` (or t
     }
     queue_to_coordinator = {"golang": "go"}
 
-``dag_bundle_name`` names the Dag bundle the coordinator scans for executable bundles. Omit it to ship the executable bundles in the same Dag bundle as the Python stub Dag. ``queue_to_coordinator`` routes stub tasks with ``queue="golang"`` to this Go coordinator. See :ref:`go-sdk/coordinator-config` for the full list of accepted ``kwargs``.
+``dag_bundle_name`` names the Dag bundle the coordinator scans for executable bundles.
+Omit it to ship the executable bundles in the same Dag bundle as the Python stub Dag.
+``queue_to_coordinator`` routes stub tasks with ``queue="golang"`` to this Go coordinator.
+See :ref:`go-sdk/coordinator-config` for the full list of accepted ``kwargs``.
 
 There is no separate Go worker to run: the Airflow worker forks the bundle binary once per task instance.
 
@@ -533,8 +536,8 @@ All ``kwargs`` in the ``coordinators`` config entry are passed to the
 
   * Leave ``dag_bundle_name`` unset (the default) to load bundles from the **task's own** Dag bundle,
     pinned to the version the run was created with.
-  * Set ``dag_bundle_name`` to load bundles from a separate Dag bundle. The task uses the version that Dag
-    bundle is on when it starts, pinned for the whole task.
+  * Set ``dag_bundle_name`` to load bundles from a separate Dag bundle.
+    The task uses the version that Dag bundle is on when it starts, pinned for the whole task.
 
 .. _go-sdk/limitations:
 

airflow-core/docs/authoring-and-scheduling/language-sdks/java.rst

@@ -274,7 +274,8 @@ Configure Airflow so the parent JAR directory is a Dag bundle, the coordinator s
     }
     queue_to_coordinator = {"java": "java"}
 
-``dag_bundle_name`` names the Dag bundle that holds the JARs. You can instead omit it and ship the JARs in the same Dag bundle as ``sales_pipeline.py``.
+``dag_bundle_name`` names the Dag bundle that holds the JARs.
+You can instead omit it and ship the JARs in the same Dag bundle as ``sales_pipeline.py``.
 
 ``java`` is a user-chosen coordinator name, not a reserved value. The value assigned to the queue in
 ``queue_to_coordinator`` must match a key in ``coordinators``.
@@ -1083,10 +1084,10 @@ All ``kwargs`` in the ``coordinators`` config entry are passed to the
 
   **Locating JARs.** JARs always live in a Dag bundle:
 
-  * Leave ``dag_bundle_name`` unset (the default) to load JARs from the **task's own** Dag bundle, pinned
-    to the version the run was created with.
-  * Set ``dag_bundle_name`` to load JARs from a separate Dag bundle. The task uses the version that bundle
-    is on when it starts, pinned for the whole task.
+  * Leave ``dag_bundle_name`` unset (the default) to load JARs from the **task's own** Dag bundle,
+    pinned to the version the run was created with.
+  * Set ``dag_bundle_name`` to load JARs from a separate Dag bundle.
+    The task uses the version that bundle is on when it starts, pinned for the whole task.
 
 .. note::
 

airflow-core/docs/authoring-and-scheduling/language-sdks/typescript.rst

@@ -238,7 +238,10 @@ variables):
     }
     queue_to_coordinator = {"typescript": "ts"}
 
-``dag_bundle_name`` names the Dag bundle the coordinator scans for ``*.min.mjs`` bundles. Omit it to ship the bundles in the same Dag bundle as the Python stub Dag. ``queue_to_coordinator`` routes stub tasks with ``queue="typescript"`` to this coordinator. See :ref:`typescript-sdk/coordinator-config` for the full list of accepted ``kwargs``.
+``dag_bundle_name`` names the Dag bundle the coordinator scans for ``*.min.mjs`` bundles.
+Omit it to ship the bundles in the same Dag bundle as the Python stub Dag.
+``queue_to_coordinator`` routes stub tasks with ``queue="typescript"`` to this coordinator.
+See :ref:`typescript-sdk/coordinator-config` for the full list of accepted ``kwargs``.
 
 There is no separate Node.js worker to run: the Airflow worker launches the bundle with ``node`` once per
 task instance.
@@ -560,8 +563,8 @@ All ``kwargs`` in the ``coordinators`` config entry are passed to the
 
   * Leave ``dag_bundle_name`` unset (the default) to load the bundle from the **task's own** Dag bundle,
     pinned to the version the run was created with.
-  * Set ``dag_bundle_name`` to load the bundle from a separate Dag bundle. The task uses the version that Dag
-    bundle is on when it starts, pinned for the whole task.
+  * Set ``dag_bundle_name`` to load the bundle from a separate Dag bundle.
+    The task uses the version that Dag bundle is on when it starts, pinned for the whole task.
 
 Limitations
 -----------

go-sdk/README.md

@@ -292,7 +292,9 @@ the full range of task states, and alternate XCom backends without implementing
   queue_to_coordinator = {"golang": "go"}
   ```
 
-  `dag_bundle_name` names the Dag bundle the coordinator scans for executable bundles. Omit it to ship them in the same Dag bundle as the Python stub Dag. `queue_to_coordinator` routes stub tasks with `queue="golang"` to this Go coordinator.
+  `dag_bundle_name` names the Dag bundle the coordinator scans for executable bundles.
+  Omit it to ship them in the same Dag bundle as the Python stub Dag.
+  `queue_to_coordinator` routes stub tasks with `queue="golang"` to this Go coordinator.
 
   > [!IMPORTANT]
   > The coordinator is part of the Airflow worker, so the `[sdk]` config (and the executable bundle

java-sdk/README.md

@@ -120,7 +120,8 @@ Now `cd example` into the example project, and
   export AIRFLOW__SDK__QUEUE_TO_COORDINATOR='{"java": "java"}'
   ```
 
-  `dag_bundle_name` names the Dag bundle that holds the JARs, here `build/bundle`, outside the Dags folder. Omit it to ship the JARs in the same Dag bundle as the stub Dag.
+  `dag_bundle_name` names the Dag bundle that holds the JARs, here `build/bundle`, outside the Dags folder.
+  Omit it to ship the JARs in the same Dag bundle as the stub Dag.
 
 * Ensure the Connection and Variable needed by the example DAG are available:
 

ts-sdk/README.md

@@ -98,10 +98,9 @@ coordinators = {
 queue_to_coordinator = {"typescript": "ts"}
 ```
 
-The stub Dag's own Dag bundle is searched recursively for `*.min.mjs` bundles built with `airflow-ts-pack`
-(see [Packing bundles](#packing-bundles)), which embeds the Airflow metadata in the bundle itself. To keep
-the `*.min.mjs` bundles in a separate Dag bundle, set `dag_bundle_name` to a bundle configured in
-`[dag_processor] dag_bundle_config_list`.
+The stub Dag's own Dag bundle is searched recursively for `*.min.mjs` bundles built with `airflow-ts-pack` (see [Packing bundles](#packing-bundles)),
+which embeds the Airflow metadata in the bundle itself. To keep the `*.min.mjs` bundles in a separate Dag bundle,
+set `dag_bundle_name` to a bundle configured in `[dag_processor] dag_bundle_config_list`.
 
 TypeScript entrypoint:
 

ts-sdk/example/README.md

@@ -83,7 +83,8 @@ export AIRFLOW__SDK__COORDINATORS='{
 export AIRFLOW__SDK__QUEUE_TO_COORDINATOR='{"typescript": "ts"}'
 ```
 
-`dag_bundle_name` names the Dag bundle that holds the bundle, here `dist/`, outside the Dags folder. Omit it to copy the bundle into the same Dag bundle as the stub Dags.
+`dag_bundle_name` names the Dag bundle that holds the bundle, here `dist/`, outside the Dags folder.
+Omit it to copy the bundle into the same Dag bundle as the stub Dags.
 
 Copy both files in `dags/` into your Airflow Dags folder.