dirigent-examples 0.17.2__tar.gz → 0.17.3__tar.gz

{dirigent_examples-0.17.2 → dirigent_examples-0.17.3}/PKG-INFO

@@ -1,13 +1,13 @@
 Metadata-Version: 2.4
 Name: dirigent-examples
-Version: 0.17.2
+Version: 0.17.3
 Summary: The dirigent example corpus: the shelves of runnable documents, installed.
 License-Expression: LicenseRef-Proprietary
 License-File: LICENSE
 Classifier: Programming Language :: Python :: 3
 Classifier: Programming Language :: Python :: 3.13
-Requires-Dist: dirigent-client==0.17.2
-Requires-Dist: dirigent-plugin==0.17.2
+Requires-Dist: dirigent-client==0.17.3
+Requires-Dist: dirigent-plugin==0.17.3
 Requires-Python: >=3.13
 Description-Content-Type: text/markdown
 

{dirigent_examples-0.17.2 → dirigent_examples-0.17.3}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "dirigent-examples"
-version = "0.17.2"
+version = "0.17.3"
 description = "The dirigent example corpus: the shelves of runnable documents, installed."
 readme = "README.md"
 requires-python = ">=3.13"
@@ -11,8 +11,8 @@ classifiers = [
     "Programming Language :: Python :: 3.13",
 ]
 dependencies = [
-    "dirigent-client==0.17.2",
-    "dirigent-plugin==0.17.2",
+    "dirigent-client==0.17.3",
+    "dirigent-plugin==0.17.3",
 ]
 
 [project.entry-points."dirigent.plugins.v1"]

{dirigent_examples-0.17.2 → dirigent_examples-0.17.3}/pyproject.toml.orig

@@ -1,6 +1,6 @@
 [project]
 name = "dirigent-examples"
-version = "0.17.2"
+version = "0.17.3"
 description = "The dirigent example corpus: the shelves of runnable documents, installed."
 readme = "README.md"
 requires-python = ">=3.13"
@@ -12,8 +12,8 @@ classifiers = [
 ]
 dependencies = [
     # The python/ shelf is SDK scripts a reader runs, so the corpus carries the client.
-    "dirigent-client==0.17.2",
-    "dirigent-plugin==0.17.2",
+    "dirigent-client==0.17.3",
+    "dirigent-plugin==0.17.3",
 ]
 
 [project.entry-points."dirigent.plugins.v1"]

{dirigent_examples-0.17.2 → dirigent_examples-0.17.3}/src/dirigent_examples/shelves/README.md

@@ -44,18 +44,19 @@ reader filters by: `schedule`, `fan-out`, `graph`, `failure`, `retry`, `timeout`
 `geocode`, `briefing`, `observability`, `conventions`, `report` for a document that
 declares a `report:` section, so every run of it writes its own account of itself, or renders
 a page of its own with `report.render`, and `starter` for a document `dg pipeline new` may
-copy into a project: a real multi-step flow on a real source, carrying nothing. A source's
-name is never a tag: the pipeline's `code` and `name` already say it is USGS or WHO GHO, and a
-word one document wears is a filter nobody can use.
+copy into a project: a real multi-step flow on a real source. A source's name is never a tag:
+the pipeline's `code` and `name` already say it is USGS or WHO GHO, and a word one document
+wears is a filter nobody can use.
 
 **The starter rule.** `starter` is the one tag a document opts into rather than wears by
 description, and it is the narrowest. A document earns it by being a real multi-step flow on
 a real source -- a public endpoint, or a service a connection names. What disqualifies one is
-a top-level `connections:` or `schemas:` section, which an instance refuses at apply; a run
-that fails by design; a single step; and a hello-world. `dg pipeline new <code>` copies a
-starter's text verbatim into `pipelines/`, rewriting only the `code:` line and dropping
-`starter` from the `tags:` line, so the comments come with it and its `requires` is the list
-of what to create first.
+a run that fails by design, a single step, and a hello-world. Carrying does not: a document
+carries its `connections:` and its `schemas:` so that `dg run --local` runs it alone, and the
+copy names them instead. `dg pipeline new <code>` copies a starter's text verbatim into
+`pipelines/`, rewriting the `code:` line, dropping `starter` from the `tags:` line, and
+moving each carried section into `requires:`, so the comments come with it and its `requires`
+is the list of what to create first.
 
 **The tiering rule.** `examples/` is what runs: every document there is runnable, though some
 need infrastructure whose setup their headers document -- the [`docker/`](docker) shelf needs a